Allow option to disable handling of form data for POST requests

[Shane32]

There is a CSRF security vulnerability that occurs when:

• Cookie authentication is in use
• The user's web browser is logged in to the vulnerable server
• The foreign origin executes a mutation against the vulnerable server (can be done via the fetch API) and includes credentials
• The data is sent via multipart/form-data so there is no CORS pre-flight check performed

I have personally verified that this CSRF attack can be exploited when cookie authentication is in use. This branch has a sample project that will successfully execute a cross-origin mutation against the Samples.Authentication project, even though the response fails CORS validation and so the response is not readable in the browser.

Sample javascript to perform the attack:

    async function executeGraphQLRequest(serverName, query) {
        const formData = new FormData();
        formData.append('query', query);
        const response = await fetch(`https://${serverName}/graphql`, {
            method: 'POST',
            body: formData,
            credentials: 'include', // Set the credentials option to "include"
        });
        const jsonResponse = await response.json();
        return jsonResponse;
    }
    async function runme() {
        const serverName = 'localhost:7110';
        const query = '{ helloRegisteredUser }';
        const jsonResponse = await executeGraphQLRequest(serverName, query);
        console.log(jsonResponse);
    }

See notes added to readme

We should set the new property to false for v9

[github-actions]

Coverage Report

Totals
Statements:	97% ( 1841 / 1898 )
Methods:	82.03% ( 283 / 345 )

[coveralls]

Pull Request Test Coverage Report for Build 10445604977

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 9 of 9 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 94.538%

---

Totals
Change from base Build 10445490527:	0.02%
Covered Lines:	1841
Relevant Lines:	1898

---

💛 - Coveralls