Auto-level AirVisual API calls

[bachya]

Proposed change

Users were reporting that monitoring multiple geographies with the same API key overran their free API limits. In the past, this was resolved by setting high scan_interval values, but since this was removed in #32072, users had no route forward.

This PR adds "self-leveling" to the API: the more clients that use the same API key, the greater the interval between API calls. The values are selected to leave plenty of buffer for the typical "free tier" use case.

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:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes Airvisual call_per_month_limit_reached #34787
• This PR is related to issue: N/A
• Link to documentation pull request: Add docs for auto-leveling AirVisual API calls home-assistant.io#13335

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

[BradleyFord]

I have updated to 110 beta0.
Within 8 hours I have hit my API limited for the day; I assume there must be some problem with the auto levelling?

[frenck]

@BradleyFord This is an open PR, which implements auto-leveling. Since it is open, it is not part of 0.110.

[MartinHjelmare]

Looks good!

[frenck]

@bachya @MartinHjelmare Should we add this to a patch release? As I've seen quite a few people running into the limits... ?

[MartinHjelmare]

Ok with me.