Add ConfigFlow for here_travel_time

[eifinger]

Breaking change

Config flow support has been added to here_travel_time. Existing YAML configuration entries will be imported automatically but should be removed from YAML configuration after import. Import support will be removed in a future release.

Proposed change

• Add ConfigFlow to here_travel_time.
• Use DataUpdateCoordinator

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 #
• This PR is related to issue:
• Link to documentation pull request: Add ConfigFlow for here_travel_time home-assistant.io#18586

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.

[AMODLT]

Que hago? No entiendo el inglés

[AMODLT]

Gracias

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[eifinger]

Still open

[frenck]

This PR implements both a config flow and a DataUpdateCoordinator, those need to be split into two separate PRs. Please, make PRs as small as possible.

[eifinger]

@frenck yes is does. And I do understand that this seems to increase the review burden. But I am convinced that the overall complexity is lower that way and faster to implement.

[frenck]

I don't agree, it is in general why PRs linger around so long, as no one wants to review it.
Neither do I, hence me asking to make small iterative changes instead.

Besides, it is against our contribution standards. Please split it.

Thanks 👍