Django-gcp

Summary

Adds a `BlobField` and corresponding widget. This allows direct to cloud uploads, as well as facilitating storage of additional blob-related metadata in JSON in the database.

Contents ([31](https://github.com/octue/django-gcp/pull/31))

New features
- Add direct upload form widget

Operations
- Add extra bucket with object verioning for demos and tests
- Widen CORS for local development and add safety note
- Prettify precommit file
- Add tailwind config to prettier
- Add container features and update container settings spec
- Add pylint extension to stop vscode nagging
- Bump version
- Fix release workflow

Other
- Add BlobField to docs

<!--- START AUTOGENERATED NOTES --->
Contents ([26](https://github.com/octue/django-gcp/pull/26))

New features
- Add Cloud Run metadata wrapper class and documentation
- Add logging handlers

Operations
- Update to latest dev stack
- Update autoformatters
- Enable build-docs to run with apidoc
- Remove channels as no asgi capability used by django-gcp
- Update version per new features

Chores
- Apply style standards and fix typos

<!--- END AUTOGENERATED NOTES --->

<!-- PRs into main are released as soon as they are merged. Their descriptions will be used directly to create release notes, so make sure they contain everything! -->
<!-- Anything added between the auto-generation marker comments will be replaced on every pushed commit, so make sure to add anything you want to add outside of them. -->
<!-- However, any part of the final PR description (i.e. the description at the point of the final commit to the PR) can be changed in release notes after release if required -->
<!-- Change "START" to "SKIP" in the autogeneration marker to stop any further automatic changes to the description. --->

Summary

Collectstatic fails when a path method is provided on the storage that overrides django's NotImplemented error but returns None (ie not an openable object on the local fs)

<!--- START AUTOGENERATED NOTES --->
<!--- END AUTOGENERATED NOTES --->

<!-- PRs into main are released as soon as they are merged. Their descriptions will be used directly to create release notes, so make sure they contain everything! -->
<!-- Anything added between the auto-generation marker comments will be replaced on every pushed commit, so make sure to add anything you want to add outside of them. -->
<!-- However, any part of the final PR description (i.e. the description at the point of the final commit to the PR) can be changed in release notes after release if required -->
<!-- Change "START" to "SKIP" in the autogeneration marker to stop any further automatic changes to the description. --->

Summary

<!--- START AUTOGENERATED NOTES --->
Contents ([19](https://github.com/octue/django-gcp/pull/19))

Fixes
- Add bucket name property to remedy backward compatibility

<!--- END AUTOGENERATED NOTES --->

<!-- PRs into main are released as soon as they are merged. Their descriptions will be used directly to create release notes, so make sure they contain everything! -->
<!-- Anything added between the auto-generation marker comments will be replaced on every pushed commit, so make sure to add anything you want to add outside of them. -->
<!-- However, any part of the final PR description (i.e. the description at the point of the final commit to the PR) can be changed in release notes after release if required -->
<!-- Change "START" to "SKIP" in the autogeneration marker to stop any further automatic changes to the description. --->

Summary

This fixes use with django < 4 where the default app config needs to be explicitly given by an app

<!--- START AUTOGENERATED NOTES --->
Contents ([18](https://github.com/octue/django-gcp/pull/18))

Fixes
- Add default app config so task manager initialised correctly

<!--- END AUTOGENERATED NOTES --->

<!-- PRs into main are released as soon as they are merged. Their descriptions will be used directly to create release notes, so make sure they contain everything! -->
<!-- Anything added between the auto-generation marker comments will be replaced on every pushed commit, so make sure to add anything you want to add outside of them. -->
<!-- However, any part of the final PR description (i.e. the description at the point of the final commit to the PR) can be changed in release notes after release if required -->
<!-- Change "START" to "SKIP" in the autogeneration marker to stop any further automatic changes to the description. --->

Summary

This release ensures that any `metadata` or `custom_time` attribute on the content object gets added to the blob on creation (or update) in google cloud, to avoid a second roundtrip to add metadata.

The method that adds this data can be overridden in a custom storage class to avoid adding it altogether or to add different data.

<!--- START AUTOGENERATED NOTES --->
Contents ([17](https://github.com/octue/django-gcp/pull/17))

New features
- Add content object metadata and custom time by default

<!--- END AUTOGENERATED NOTES --->