Django-aws-api-gateway-websockets

- Added in tests for Python 3.11
- Removed use of CodeCov and moved to use GitHUb actions to store and report on the coverage.
- Actions fail if coverage drops below 85%, this threshold will be increased in the future as I add in additional tests
- Updated requirements and removed legacy tox files
- Updated version of gitHub Actions
- Added link to the PyPi site from the readme

- Updating the listing pages to include whether the additional route has been deployed or not
- Updated the README file

- Added support for additional custom routes for each API. This means that you could use one API Gateway for an entire
project if you wished to using the ApiGatewayAdditionalRoute to route requests to different URLs within your
project. This is extremely useful if you have multiple apps that require websockets. The recommendation is to have a
central view that handles all connections, disconnections and the default route. Then to use specific route for each of
your apps, views or however you require to separate requests.

- Added in additional unit tests. Still requires additional tests for full coverage

- BUG FIX - The _create_domain_name method of the ApiGateway was always setting a hosted zone id even if one
was not to be used.
- Updating the README.md file with the updated IAM policy

- Updating the packaging of the project as the management command was not being bundled with the rest of the code.