Widen supported django and python ranges, update developer tools

[thclark]

Contents (#71)

IMPORTANT: There is 1 breaking change.

Fixes

• Use newer accessor for django settings
• 💥 BREAKING CHANGE: Avoid circular import of StreamHandler in some python environments
• Correctly parameterise tox dependency installation
• FFS
• Tighten django ranges

Operations

• Update devcontainer onto latest stack
• Fail slow on matrix so we can detect problems with specific builds
• Update tox versions
• Remove unused tox-poetry plugin
• Enable testing using example buckets in GitHub Actions, via WIF
• Refine test matrix, remove tox-factor, no longer required in tox 4
• Add credentials generation for Workload Identity Federation
• Try to get poetry to install dev dependencies
• Ditch the tox bitch
• Fix the pre-commit run
• Remove pre-commit-sphinx local install for use on GHA
• Exclude invalid python-django combinations
• Skip pre-commit checks invalid for GHA
• Bump version
• Add django env vars
• Add application credentials to environment
• Temporarily constrain django version
• Add a check-main-merge test
• Simplify merge check
• Update cache to a non-deprecated node runner
• Change order of publish-test so it appears above long test matrix
• Update cache action version
• Rename job for clarity

Dependencies

• Widen python and django tested versions
• Restrict django 5.1 until STORAGES problem solved
• Update lockfile
• Remove django 3 support

Testing

• Patch the error reporting emitter
• Remove now-unused tox file
• Avoid utc import from django timezone

Style

• Fix all linting problems

Other

• Toward allowing ci to run on push to main

---

Upgrade instructions

💥 Avoid circular import of StreamHandler in some python environments

The django_gcp.logging module has been renamed to django_gcp.logs because some python environments (eg installed in tox) don't resolve the import order in the same way, so mistake django_gcp.logging for the inbuilt python logging module. To overcome this, users of the structured logging or error reporting handlers must update their handler classes to 'django_gcp.logs.GoogleStructuredLogsHandler' and 'django_gcp.logs.GoogleErrorReportingHandler' from the previous 'django_gcp.logging.'

[thclark]

@cortadocodes I know all the tests are failing here, they're mostly failing on 2-4 tests, many of which are due to needing to patch the queue. But I've asked for a review mostly because I'm looking for what you think of the new ci workflow.

Note: publish-test done in parallel to tests because, in this moment at least, I wanted to know it passed even though tests are failing

Also note: I'll probably squash a whole bunch of these commits, forgive the fairly crazy commit history. Usual trial-and-error BS of working with GHA, you know?!

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 68.04%. Comparing base (ab44d54) to head (6fa5367). Report is 144 commits behind head on main.

Files with missing lines	Patch %	Lines
django_gcp/tasks/manager.py	0.00%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #71 +/- ## =========================================== - Coverage 90.04% 68.04% -22.01% =========================================== Files 23 41 +18 Lines 824 1862 +1038 =========================================== + Hits 742 1267 +525 - Misses 82 595 +513 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.