Add options flow to OpenSky

[joostlek]

Proposed change

Add Options flow to Opensky.

In the options flow, users can fill in their username and password to authenticate and upgrade their update interval.

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 #
• This PR is related to issue:
• Link to documentation pull request: Add info about Opensky authentication home-assistant.io#28642

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.

[edenhaus]

We should either allow the user to insert a username/password during the initial config flow or update the docs to inform the user about the ability to configure the username/password.
Otherwise, the user doesn't know about it.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[joostlek]

Oh right, I still have to open a docs PR. Did you take a look at the rest of the code already?

[edenhaus]

Oh right, I still have to open a docs PR. Did you take a look at the rest of the code already?

Yes, the rest is fine. I wanted to know if you prefer to open a docs PR or add the username/password to the initial setup.

[joostlek]

I think I prefer this way as it's not needed for the API to be authenticated, this way I don't force all users to login to a service they never had to