[DEV-103519] Upgrade to Django 4.2. Switch from travis to GHA

[JVenberg]

What is the reason for this PR?

We are upgrading this library to support Django 4.2. As a result, we are updating the requirements to be Python>=3.8 and Django >=3.2

We no longer use travis to run our CI/CD tests. Our standard here at Rover is to use Github Actions. This switches the testing of different python versions over to GHA.

Validation

How will we know this is working?

• This PR should have all tests passing.
• After merging, the master branch should have all tests passing

[sayhiben]

Approved with the caveat that the Django 4 tests are failing due to what looks like a migration step that needs to be taken

[sayhiben]

lgtm! Sorry if I led you down a rabbit hole with the cache; I didn't think it was going to be a PITA

[pearsondaniels]

How did we settle on these options?

[JVenberg]

I am not actually sure. I merged in @facundojmaero's PR here and he had changed a few things. I assume it was to either get it to lint with the newer linter version and/or due to the formatting changes he made

[pearsondaniels]

Oh gotcha. Yeah like the max line length change, for example. Not a huge deal since its just linting.

[sshishov]

I would recommend you to migrate to ruff and deprecate all isort, flake8, pylint/black etc...

But it is up-to-you, just ruff is blazing fast and making what it should do without issues...

[pearsondaniels]

Overall looks ok to me, just a question on some of the config. I don't have the Travis config for reference

[JVenberg]

Overall looks ok to me, just a question on some of the config. I don't have the Travis config for reference

Here is all we removed regarding Travis. I don't know if we've had a Github Travis integration for a long while