Improve IQVIA data/API management based on enabled entities

[bachya]

Proposed change

#32223 deprecated monitored conditions within IQVIA. Since the integration derives its data from several API calls, this PR goes a step further and improves its data management so that as entities are enabled/disabled, the appropriate API calls are also enabled/disabled.

Additionally, this PR removes some useless warning messages.

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
iqvia:
  zip_code: !secret zip_code

Additional information

• This PR fixes or closes issue: N/A
• This PR is related to issue: N/A
• Link to documentation pull request: N/A

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

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (dev@d36259f). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev   #32291   +/-   ##
======================================
  Coverage       ?   94.74%           
======================================
  Files          ?      772           
  Lines          ?    55935           
  Branches       ?        0           
======================================
  Hits           ?    52995           
  Misses         ?     2940           
  Partials       ?        0

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d36259f...9927577. Read the comment docs.

[balloob]

async_added_to_hass should not trigger an update.

[bachya]

Without this, the entities show unavailable until their next update cycle. With this "API registration" mechanism in play, I'm unclear on how to instruct an entity to update immediately after its data is pulled (which occurs when "interest" is registered first) without this.

[bachya]

@balloob How do you feel about c41edf1?

[balloob]

Ok to merge when last comment addressed 👍