Hello,,

The [new Celery 5.0](https://docs.celeryproject.org/en/stable/whatsnew-5.0.html) has been released and we may consider migrating to this version. I don't know if it has to happen now, if we should wait for version 5.1 or do it now. I am creating this ticket to track this version.

To process this issue, we should consider the consequences of this update, update the CLI calls, update API calls, and test these versions thoroughly.

@auvipy Can you tell a little more about this release? Is this release stable enough to update our project to these versions?  What consequences could this update have?

setup.py
"""
    List all available extras
    Registered as cmdclass in setup() so it can be called with ``python setup.py list_extras``.
    """
    description = "List available extras"
    user_options: List[str] = []
    def initialize_options(self) -> None:
        """Set default values for options."""
    def finalize_options(self) -> None:
        """Set final values for options."""
    def run(self) -> None:
        """List extras."""
        print("\n".join(wrap(", ".join(EXTRAS_REQUIREMENTS.keys()), 100)))
def git_version(version_: str) -> str:
    """
    Return a version to identify the state of the underlying git repo. The version will
    indicate whether the head of the current git-backed working directory is tied to a
    release tag or not : it will indicate the former with a 'release:{version}' prefix
    and the latter with a '.dev0' suffix. Following the prefix will be a sha of the current
    branch head. Finally, a "dirty" suffix is appended to indicate that uncommitted
    changes are present.
    :param str version_: Semver version
    :return: Found Airflow version in Git repo
    :rtype: str
    """
    try:
        import git
        try:
            repo = git.Repo(os.path.join(*[my_dir, '.git']))