Add ability to handle correctly OPTIONS and HEAD requests

[girardinsamuel]

This PR adds:

OPTIONS request handling

Before, if a route with OPTIONS had not been defined, a request to an existing route with OPTIONS method was returning a 404 Not Found. Now, it's returning a 204 No Content response with Allow headers containing the allowed request methods for this route.

(ref https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/OPTIONS#identifying_allowed_request_methods)

Method Not Allowed handling

Before if a route was accessed with wrong request method, it was returning a 404 Not Found. Now if the route exists but accessed with wrong methods, it will return a 405 Method Not Allowed exception with error message containing the allowed request methods for this route.

HEAD request handling

Before, if a route with HEAD had not been defined, a request to an existing route with HEAD method was returning a 404 Not Found. Now, it's returning a 204 No Content response with the headers that would have been sent if the request had been made with GET method.

(ref https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD)

In addition, when defining a GET route, Masonite will automatically add a HEAD route for it.

Here is a summary with CURL commands against a Masonite app:

For this, two small features have been added:

• adds withHeaders to response to add headers as a dict easily, as header() was one header by one and was not returning response class
• adds ability to add headers to HTTP exception when rendering exceptions.

[girardinsamuel]

@josephmancuso can you take a look at this? This PR is required for the CORS feature 😉.

[josephmancuso]

code review good. Just want to test this manually before merging