Add authorisation functionality to OpenSky Integration

[OzGav]

Breaking change

Users of the integration must now supply a username and password. Currently anonymous users only get 400API calls per day which equates to one every 3.6 minutes which isn't useful when tracking aircraft. Registered users are allowed 4000 requests per day or one every 21.6 seconds. Therefore, the integration is only useful for registered users and thus there is now a requirement to supply credentials.

Proposed change

The integration currently makes an API call every 12 seconds which will result in the 400 API calls allowed being exhausted after 80 minutes. The integration will then crash when JSON is not returned. This fault has been the subject of numerous issues over the last few years. The most recent is here #45453
This PR adds the ability to enter a username and password into the config and then authorise the session.

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)
• Deprecation (breaking change to happen in the future)
• 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 # Update for sensor.opensky fails #43571 opensky with Update Error #45453 Opensky - Sensor creation error over last fortnight #74935 Update needed home-assistant.io#23703
• This PR is related to issue: As above
• Link to documentation pull request: Update opensky.markdown home-assistant.io#26936

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
• I have followed the perfect PR recommendations
• 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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[OzGav]

I'm new at this but this simple change is working well for me

[frenck]

We no longer allow integrations to add or change a platform YAML configuration.

More information on this can be found in Architecture Decision Record:

• ADR-0007: https://github.com/home-assistant/architecture/blob/master/adr/0007-integration-config-yaml-structure.md#decision

Please note that this integration connects to a device or service and another Architecture Decision Record applies that disallows the use of YAML configuration in favor of a configuration flow via the UI:

• ADR-0010: https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md#decision

See our developer documentation on how to get started creating a configuration flow for this integration:

https://developers.home-assistant.io/docs/config_entries_config_flow_handler

As these changes often involve a bit of work and some significant shift in the current code, we will close this PR for now.

We (and our community!) would really appreciate it if you could start on the refactoring of this integration in a new PR.

Thanks already! 👍

[OzGav]

Yeah sorry @frenck i don’t think I have the technical skills to do the refactor…..