Fix ZHA websocket API test

[TheJulianJES]

Proposed change

This fixes an issue where the ZHA websocket test did not compare the websocket API configuration to the expected configuration, but instead always to itself, as the initial config was always overwritten.

This issue was noticed by @autinerd here: https://github.com/home-assistant/core/pull/114470/files/821eec8e2ce01bbda204c095f16dc5154bc4ab20#r1545303606

Background on the change:

As we do not use device_ias_ace fixture in this test (thus "no alarm device in the network"), ZHA does not add alarm config options anymore, so they won't be in the final config that you get from the websocket API.
As this test uses the initial config to compare to (just modifies the light transition part to update one config option), we now use the base config without alarm options instead of the one with alarm options.

An alternative solution would be to add the device_ias_ace fixture to the test and compare to CONFIG_WITH_ALARM_OPTIONS, but the test above this one already tests that functionality, so I don't see much reason in duplicating that into this test too.

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

Code owner commands

Code owners of zha 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 zha 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.

[puddly]

Good catch, @autinerd, and thanks @TheJulianJES for fixing this!