Add lock platform to Volvo integration

[thomasddn]

Proposed change

Add lock platform to Volvo 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: https://github.com/orgs/home-assistant/discussions/1253
• Link to documentation pull request: Add lock documentation for Volvo integration home-assistant.io#41273
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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.

[raido]

👋 Hello, just sharing recently opened discussion to link things together.

Glad to see recent actions/buttons and device tracker features. 🎉

[gjohansson-ST]

Codes looks fine but I'm hesitant to make two locks for the same lock
Should this not be one lock and possibly something else to set if it's full lock or reduced? Not sure myself was is the better approach.

[thomasddn]

Thanks for the feedback @gjohansson-ST!

In the Volvo app there is one dedicated lock/unlock button. Next to it, there's a select with the following options: Lock, Lock with reduced guard, Unlock trunk.

To mimic this approach we could also have on lock entity and then a button that does the "Lock with reduced guard". Also, there is no way to tell afterwards how the car was locked. So the button could be a fit.

(Unlock trunk is not possible with the API.)

[gjohansson-ST]

In the Volvo app there is one dedicated lock/unlock button. Next to it, there's a select with the following options: Lock, Lock with reduced guard, Unlock trunk.

To mimic this approach we could also have on lock entity and then a button that does the "Lock with reduced guard". Also, there is no way to tell afterwards how the car was locked. So the button could be a fit.

Initially I was thinking maybe a select entity for selecting the "mode" but probably not a bad idea to make a button instead for the reduced mode option and don't have to mess with a select entity.

[thomasddn]

I have removed the "reduced guard" lock from this PR. I'll create a new PR later to add this "reduced guard" as a button.

[gjohansson-ST]

Thanks @thomasddn 👍