Add Energyzero get_prices service

[iamrgroot]

Proposed change

Follow-up of #100370 (comment)

This PR adds a service that returns the energy and gas prices as response. This allows someone to put it into a template sensor:

template:
  - trigger:
      - platform: time_pattern
        hours: "*"
    action:
      - service: energyzero.get_prices
        data:
          type: energy
        response_variable: prices
    sensor:
      - name: Response
        device_class: timestamp
        state: "{{ now() }}"
        attributes:
          prices: '{{ prices }}'

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 Energyzero get_gas_prices and get_energy_price services home-assistant.io#28943

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 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 @klaasnicolaas, mind taking a look at this pull request as it has been labeled with an integration (energyzero) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of energyzero can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign energyzero Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[iamrgroot]

@klaasnicolaas do you maybe have some time to look at this pr?

[edenhaus]

Please make sure CI is passing

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

[edenhaus]

Btw your example can be simplified by using actions in your template

[iamrgroot]

@edenhaus can I fix this CI run myself? https://github.com/home-assistant/core/actions/runs/6300571239/job/17106518193

[edenhaus]

@edenhaus can I fix this CI run myself? home-assistant/core/actions/runs/6300571239/job/17106518193

Nope only members can retrigger the job.

[iamrgroot]

@edenhaus is there any way to get this though without a review from the code owner (or am I being a bit too eager)?

[klaasnicolaas]

By waiting patiently and no, we are certainly not going to just skip the code owner just to get a PR through 😉

[klaasnicolaas]

✅ Approved, don't see anything strange in the code at the moment

[joostlek]

Final remark

[edenhaus]

Thanks @iamrgroot 👍

[frenck]

@edenhaus @iamrgroot @klaasnicolaas I want to revert this PR, as I think the approach is wrong.

Let me make a revert and explain why in the revert PR.

../Frenck

[iamrgroot]

@frenck this already was a different approach that was suggested by you in #100370

Let me know what to do differently and I'll try again

[frenck]

@iamrgroot Yup. This is the right direction though, but we should not have merged this.

../Frenck