Replace access token authentication with OAuth2 in Teslemetry

[Bre77]

Breaking change

Teslemetry will no longer use the provided access token, and instead will be automatically migrated to an OAuth registration. You can manage your application registrations on the Teslemetry Console.

Proposed change

Teslemetry Config Flow is now version 2, and is a PKRE OAuth2 implementation using a hardcoded client ID and no client secret. This removes the need for the user to copy and paste an access token (which surprisingly was causing friction), and now uses a simple OAuth2 flow.

Needs #159056 and #159048 which have been rebased into this PR so that its functional.

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:
• Link to developer documentation pull request: Reflect OAuth usage in Teslemetry home-assistant.io#42551
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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 Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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.

To help with the load of incoming pull requests:

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

[Bre77]

I'm not 100% sure if this is actually a breaking change, its a major change, but I built a migration path that should be seemless.

[Bre77]

Test failure is unrelated

[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.