Add support for Django 4.2 and 5.0, and drop support for prior versions

[pamella]

Description

• Add support for Django 4.2 and 5.0, and drop support for prior versions.
  • https://www.djangoproject.com/download/
    
  • https://docs.djangoproject.com/en/5.0/faq/install/#what-python-version-can-i-use-with-django
    
• Replace Travis with GitHub Actions.
• Replace codecov with coveralls.
  • https://coveralls.io/github/vintasoftware/django-celerybeat-status
• Refactor code to reflect newer versions of Python and Django.
• Run black and isort.
• Add badges to README.
• -Add Contributing section to README.

ℹ️ Related to #23.

Related issues

• Closes Fixed typo #20
• Closes Bump celery from 4.1.0 to 5.2.2 #22
• Closes Implement support for django 4 #23

Screenshots

• Run the project.
• Check if the admin pages are working properly.

Screencast.from.16-05-2024.19.16.15.webm

[fjsj]

Do we need to keep this manage.py?

[fjsj]

In django-virtual-models, I have a separate example folder: https://github.com/vintasoftware/django-virtual-models

[pamella]

I'll check

[pamella]

I believe folks did it like that because of the need to add celerybeat_status to INSTALLED_APPS.

[pamella]

Would renaming the tests folder to example be a middle ground?

[pamella]

I'm trying to find an example with the manage.py, but so far I believe we have it so we can run and render the admin UI for testing/QA purposes.

[fjsj]

Having a tests folder is fine, but that's where the tests are, not the examples.
The idea for having a tests dir is to not distribute it along with the main app (it's not installed via pip for example)

[pamella]

I see, but the tests folders have auxiliary files besides the test_* ones. For example:

• django-rest-framework has models.py and urls.py.
• django-cors-headers has settings.py and urls.py.

We would be doing something similar here

[fjsj]

yes, that's fine

[fjsj]

Django own code also does this.

[fjsj]

Overall LGTM. What's missing?

[pamella]

Overall LGTM. What's missing?

The TODO items from the description:

• Add GitHub action to address the release process.
• Update README with the new Django syntax and instructions on how to run/contribute to this project.

[pamella]

@fjsj The PR is ready for review. I will add the release GitHub action in another PR.