Add device triggers to the Monzo integration

[JakeMartin-ICL]

Proposed change

This adds device triggers to the Monzo integration, allowing triggering automations when a transaction is made on an account.

To achieve this, webhooks are registered during setup with the Monzo API for each account, which fires an event, which triggers the device trigger. The webhooks are tidied up on integration removal and at each start and teardown we clear all webhooks from the Monzo API matching the host associated with this instance.

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: Add device trigger docs for Monzo integration home-assistant.io#33162

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.

[home-assistant]

There is a merge conflict.

[joostlek]

This code looks familiar :P

Instead of using device triggers, have you considered using event entities?

[JakeMartin-ICL]

I've extracted the dependency bump and the change to config_entries into their own PRs to go in first:

• Bump monzopy to 1.3.0 #119225
• Move runtime_data deletion after unload #119224

[JakeMartin-ICL]

This code looks familiar :P

Instead of using device triggers, have you considered using event entities?

Yep, thanks for setting great examples :D

Yeah, but although I like the everything-is-an-entity model on the backend, I think device triggers are much more intuitive for users on the frontend, at least for now.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

Stale

[emontnemery]

@JakeMartin-ICL To make this PR move, address the review comments, and don't forget to click the "Ready for review" button when you want the PR to be reviewed again. If you don't agree or understand some comment, reply to it.

[emontnemery]

The added webhook management is lacking in test coverage, can that be improved?
Also, please add translations in monzo/strings.json for the device trigger

[emontnemery]

Please consider the new review comments, and don't forget to click the "Ready for review" button once you've addressed them.