Reword invoke_pin action to avoid misunderstanding with "PIN"

[NoRi2909]

Proposed change

The previous mismatch between "PIN" and "pin" in the invoke_pin action caused wrong translations as "PIN" was interpreted as the abbreviation for "Personal Identification Number".

This commit fixes this by explaining "pin" as related to "pinning" content on the device.

In addition the very technical term "invoke" is replaced by "play" which every user and translator will understand immediately.

Along with those changes this PR reverts my previous PR to use "PIN" in all strings that made things worse.

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:

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.

[home-assistant]

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

Code owner commands

Code owners of openhome 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 openhome Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[zweckj]

What about the other pins? Can those stay caps?

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

[NoRi2909]

@zweckj As suggested by @bazwilliams I changed all occurences of "PIN" to "pin" so it no longer looks like the abbreviation.

There are six Pins on the device and Linn's docs also use both spellings.

Here a mockup of all the changes in the UI:

[zweckj]

That one I'm happy with, the others could still be improved imo -> check suggestions

[NoRi2909]

@zweckj Everything contained in the strings.json is visible in my mockup above.
There are no other strings left as it contains this action, only.

So if the mockup is OK with you and @bazwilliams there is nothing left to change?