New Laravel Cheat Sheet

[paras-malhotra]

Checklist:

• In case of a new Cheat Sheet, you have used the Cheat Sheet template.
• All the markdown files do not raise any validation policy violation, see the policy.
• All the markdown files follow these format rules.
• All your assets are stored in the assets folder.
• All the images used are in the PNG format.
• Any references to websites have been formatted as TEXT
• You verified/tested the effectiveness of your contribution (e.g., the defensive code proposed is really an effective remediation? Please verify it works!).
• The CI build of your PR pass, see the build status here.

Closes #527.

I'm leaving this open until next week to invite feedback from the Laravel community. I'll tweet about this and get some reviews going!

In the meantime, feel free to provide feedback on this. This is my first CS. I've tried to cover as much as possible and based the structure off the Ruby on Rails CS.

[jmanico]

Looks good but I see the error message:

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

[jmanico]

Looks good but I see the error message:

This commit does not belong to any branch on this repository and may belong to a fork outside of the repository.

[paras-malhotra]

@jmanico, the commits will be pulled in once this PR is merged. I think the issue may be that I added this to the master branch of my fork instead of creating a separate branch.

[paras-malhotra]

@jmanico, I've consulted some Laravel folks and this looks good to go! Let me know if you'd like me to make any changes.

[jmanico]

What a huge and solid effort. The changes I'd like to suggest are not blocking so I'll approve and merge