Bump aiopulse to 0.4.6

[atmurray]

Breaking change

Proposed change

Non-breaking changes to fix isses:

• eliminating hub exceptions raised due use of unicode strings.
• eliminating hub exceptions raised due to Timers being configured on hub.
  ...by moving from aiopulse 0.4.4 to aiopulse 0.4.6 with the following changelog:
  https://github.com/atmurray/aiopulse/releases/tag/v0.4.6
  https://github.com/atmurray/aiopulse/releases/tag/v0.4.5

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.

To help with the load of incoming pull requests:

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

[epenet]

Should this be included in 2024.9?

[atmurray]

Would be nice, its a non-breaking change that resolves a couple of issues that have been problematic for a few users.

[joostlek]

Massive thanks for splitting the PRs btw. A lot of people see this as overhead, but now we can at least get some fixes in, while others wait for discussions :D