Use issue_registry fixture in component tests

[epenet]

Proposed change

SSIA
Also, make sure that issue_registry is imported as ir and avoid importing items directly from issue_registry namespace.

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:

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

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.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[thecode]

What is the benefit in using this kind of import? Looking at all the other import we import just the class we use, what is the difference in this case?

[frenck]

There is no benefit, but is standardize across our eco system (see also the definition of all registries in pyproject.toml

[epenet]

We have such short namespaces for area/device/entity/issue registries.
It is mostly to standardize, and avoid such things as:
from homeassistant.helpers.issue_registry import async_get as async_get_issue_registry

[frenck]

Looks good to me 👍

../Frenck