New CS: GraphQL Security Cheat Sheet

[bigshebang]

This PR covers issue #421

Don't crucify me, but I didn't check for any policy violations or use the New CS template. Just wanted to get my content here first as quickly as I could. I did check up with the conversion rules though and should be compliant with that.

This content is a copy (with small editing) of a quick cheat sheet I made for developers. I made this probably the same day that I started actually learning about breaking GraphQL and I'm still not very experienced testing it. I drew from online content like OWASP and Apollo GraphQL and from colleagues with more experience breaking GraphQL.

Some definite improvements that can be made:

• Update format/layout to conform more with OWASP CS format
• Some wording is uncertain due to unfamiliarity with GraphQL; this should be made to sound more confident
• Actual code or config examples/snippets would probably be helpful
• There are probably other hardening areas or potential attacks to consider that I missed

[ThunderSon]

Had an initial quick skim over this. It looks like a nice place to grow it out into a beautiful CS. No crucifying for now.
The CS layout format is a really simple thing, we'll take care of that and send commits on this PR.

Set in draft mode till we're a bit more convinced on the structure and the potential of what it could contain.
Once we're done with that, we'll add it.

Next stage a larger expansion of it.

So first, have a robust skeleton with the details in there and with additional research. Second, making this into a full CS that is ready for production.

[jmanico]

No crucifying for now. Our good friend ThunderSon meant to say, no crucifying *ever* and we are grateful for your volunteer efforts!! =) Aloha, Jim

[mackowski]

I like it so far! I will add some comments after @ThunderSon will update structure/format. Good job @bigshebang!

[bigshebang]

Thanks all! Excited to get this CS out there for the world to use.

[ThunderSon]

@bigshebang please create a new PR with a new branch. Master branches aren't fun playing with when things go sideways :)

[bigshebang]

Moving this to a different PR with a new branch.

[bigshebang]

See new PR here: #434.