Add binary sensor to madVR integration

[iloveicedgreentea]

Proposed change

This adds binary sensors to the madvr integration

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: Madvr home-assistant.io#33401

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.

[joostlek]

Take a

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

[iloveicedgreentea]

redid to use entity description please let me know if that is correct

[joostlek]

Please look into translated names. When the entities have a translation key you can use icon translations to easily change the icon. Also please keep the order of 1. Sensor definitions 2. Async setup entry 3. Sensor classes.

A base class will definitely help you for the future

[iloveicedgreentea]

implemented a base entity and changed it to use translation keys

[joostlek]

Wrong button

[iloveicedgreentea]

added parameterized tests, access update function from mock, misc fixes

[iloveicedgreentea]

docs PR home-assistant/home-assistant.io#33659