Add Yamaha MusicCast Select Entities

[micha91]

Proposed change

After we already added number entities for configuration purposes the following select entities will be made available for MusicCast devices supporting them.

Device specific entities:

• Dimmer
  • Set the display brightness

Zone specific entities:

• Surround Decoder Type
  • If sound program is set to surround decoder, the decoder type can be selected here
• Sleep
  • Set a sleep timer for the device
• Equalizer Mode
  • Some devices support multiple different equalizer modes
• Tone Control Mode
  • Some devices support multiple different tone control modes
• Link Audio Delay
  • Some devices let the user select, whether he wants to have audio and video in sync or the linked speakers of a group
• Link Control
  • Some devices support compressed audio for groups
• Link Audio Quality
  • Set the audio quality for grouped speakers

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add Select Entities to MusicCast Documentation home-assistant.io#20523

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

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[probot-home-assistant]

Hey there @vigonotion, mind taking a look at this pull request as it has been labeled with an integration (yamaha_musiccast) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[emontnemery]

Looks good, but please fix the translations

[micha91]

Looks good, but please fix the translations

Thanks for the hint. I did not realize that we also work this way for status values, but I like that 👍

[emontnemery]

Thanks, @micha91 👍

[MartinHjelmare]

Please address the comment in a new PR. Thanks!

[MartinHjelmare]

Please define the valid device classes in a container here in the platform and validate the device class before returning it. The device class is a Home Assistant API so we need to be in control and make sure it is correct before returning it.