Downgrade setuptools to fix CI

[KapJI]

Proposed change

It seems pypa/setuptools#2640 in setuptools 56.2.0 broke installation for some packages. Use older version as a workaround.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes CI is broken because of setuptools #50733
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[KapJI]

I think after Github Actions outage they flushed caches and this issue emerged.

[KapJI]

Jinja2 was recently updated to version 3.0.0 which improved typing support, to fix mypy we need to remove some redundant stuff.

[KapJI]

No idea how codecov was triggered on files which I didn't touch.

[janiversen]

I suppose it is because it run over all files as defined in the ini file.

Apart from that, does setup tools use freesms ? (CI breaks down in freesms==0..1.2)

[cdce8p]

Apart from that, does setup tools use freesms ? (CI breaks down in freesms==0..1.2)

@janiversen No, setuptools doesn't. However we install it as part of the CI job for later tests and the install itself fails. The reason is that it has an ill-formatted license field. bfontaine/freesms#7 will fix that, but freesms might not be the only package that is failing.

[janiversen]

thanks for the explanation, looking forward to this PR being merged, so we can get CI operational again.