Use SCAN_INTERVAL instead of Throttle for google travel time

[shidarin]

Proposed change

The documentation for google_travel_time was at odds with the implementation. The documentation stated a default scan time of 5 minutes, but the implementation was using Throttle which resulted in the sensor updating at a maximum rate of one API call every 5 minutes. This was especially at odds with a given example at the end of the documentation, which showed updating the sensor every 2 minutes during commute times.

This change brings the implementation in line with the docs by adopting the SCAN_INTERVAL constant set to the stated default of 5 minutes and removing the Throttle.

This PR maintains the current default of 5 minutes, but fixes the bug where lower scan_intervals would not be respected.

In fixing this issue I also looked at #31167 which adds scan_interval support for the NUT integration. I'm unclear if this, or that approach is the preferred implementation method.

Also of note is that I've completely removed the Throttle here. Given that this uses a Google Cloud platform API which could result in user charges, I considered keeping a Throttle set to 15 seconds or so to limit potential damage. This can be easily added if requested.

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

Example entry for configuration.yaml:

This code snippet will now work- updating once a minute.

sensor:
  - platform: google_travel_time
    name: Home to Work
    api_key: #big secret
    origin: Address
    destination: Another address
    scan_interval: 60

Additional information

• This PR fixes or closes issue: fixes google_travel_time implementation at odds with documentation #31384
• This PR is related to issue: google_travel_time implementation at odds with documentation #31384
• Link to documentation pull request: The documentation found here is now correct

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.

No tests exist for this integration.

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

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

As this PR brings the code up to matching the documentation, docs did not need updating.

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

[probot-home-assistant]

Hey there @robbiet480, mind taking a look at this pull request as its been labeled with a integration (google_travel_time) you are listed as a codeowner for? Thanks!

[elupus]

Non-maintainer ok.