Add log level changed message when user changes Z-Wave JS log level

[raman325]

Proposed change

This is similar to #9062 in that when the user changes the log level on the logging UI page, there's no feedback to confirm that the log level actually changed. When you go from a more noisy to a less noisy log level in particular, it almost seems like something was broken.

I fixed a a bug that this exposed where you can't go back to the original log level that was set when you first loaded this page without a hard refresh. This is because we never updated the stored logConfig so setting it back to the original would
return early.

CC @cgarwood

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion: Add "subscribed to log" message on Z-Wave JS log subscription #9062
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• 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

[raman325]

Right now, I am updating the stored log level in the stored log config directly, but we could call _fetchData instead and retrieve the entire object from the server, with the idea being that theoretically the config could have been changed elsewhere. Only problem is that based on that logic, we will only know about the change when the user changes the dropdown.

I've proposed adding an upstream event that gets sent whenever the log config gets updated that we could subscribe to here to keep the state up to date even if the config was changed elsewhere. That would also fix this bug. zwave-js/zwave-js#2672

[cgarwood]

I think this approach is fine. If a person is on the log view page, there's (in theory) little chance they'll change the log level somewhere else and not know or realize they changed it.