[SECURITY] Previous Auth Name in nukiopener/lock/json

[alexlenk]

PROBLEM DESCRIPTION

A clear and concise description of what the problem is.

In the nukiopener/lock/json transmitted to the MQTT broker the "auth_name" field is not up to date. It is from the last opening action and not the current one. This means that checking for who opened the door and execute action based on this will result in wrong access right.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• [ ] Read the Contributing Guide and Policy and the Code of Conduct
• [ ] Searched the problem in issues
• [ ] Searched the problem in discussions
• [ ] Searched the problem in the docs
• [ ] Searched the problem in the chat
• [ ] Device used (e.g., ESP32-S3): _____
• [ ] Nuki Hub binary firmware version number used: _____
  • [ ] Pre-compiled
  • [ ] Self-compiled
• [ ] Provide the output of http://nukihubIP/info:

### TO REPRODUCE
_Steps to reproduce the behavior:_

1. Open the Nuki Opener via MQTT/HomeAssistant. This changes the Auth Name to: "NukiHub"
2. Open the Nuki Opener with the App or Keypad. In this MQTT message should now the authenticated user be set as "Auth Name". It is, however, still "NukiHub"

### EXPECTED BEHAVIOUR
_A clear and concise description of what you expected to happen._

Have the correct Auth Name from the person who executes the action

### SCREENSHOTS
_If applicable, add screenshots to help explain your problem._

### ADDITIONAL CONTEXT
_Add any other context about the problem here._

**(Please, remember to close the issue when the problem has been addressed)**

[iranl]

Please complete the template as required by our code of conduct. This will help exclude misconfiguration on your part as a cause of the issue.