Add quarter-hour peak consumption sensors

[Glodenox]

Proposed change

Release 5.9.0 of DSMR Reader adds the option to expose the quarter-hour peak electricity consumption information via MQTT. This PR adds these 3 values as new sensors.

Just for some context: next year, the cost of electricity in Belgium will be partially influenced by the peak consumption. An average of the consumption is taken for each block of 15 minutes and the highest average of each month is used to calculate part of the invoice. The idea is to encourage people to spread out their electricity consumption. It's not a big factor though, so the impact on the invoice is still quite limited. There is almost certainly going to be another update to DSMR Reader in the coming months, as the data has very recently become available within the meter's datagrams. Right now, DSMR Reader still does the calculation by itself.

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 DSMR_Reader: not creating sensors for mqtt topic 'dsmr/consumption/quarter-hour-peak-electricity' #83999
• Link to documentation pull request: Add quarter-hour peaks data source to dsmr_reader home-assistant.io#25356

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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @depl0y, mind taking a look at this pull request as it has been labeled with an integration (dsmr_reader) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of dsmr_reader can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign dsmr_reader Removes the current integration label and assignees on the issue, add the integration domain after the command.

[frenck]

Thanks, @Glodenox 👍

Happy Holidays! 🎄

../Frenck