Upgrade Verisure to 2.6.6

[niro1987]

Proposed change

• bump vsure==2.6.6 (changelog, this enables the trust cookie)
• attempt reauth using trust cookie in _async_update_data

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 Verisure integration keeps logging out #97885

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 Black (black --fast 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 @frenck, mind taking a look at this pull request as it has been labeled with an integration (verisure) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of verisure 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 verisure Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[niro1987]

@gjohansson-ST
For your info; after rebase I got this error from the migration. Might be nothing, but still wanted to let you know.
The integration did not load and had to be removed/added to fix the error.

2023-08-16 07:49:43.246 ERROR (MainThread) [homeassistant.config_entries] Error migrating entry *SANITIZED* for verisure
Traceback (most recent call last):
  File "/workspaces/homeassistant-core/homeassistant/config_entries.py", line 633, in async_migrate
    result = await component.async_migrate_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspaces/homeassistant-core/homeassistant/components/verisure/__init__.py", line 97, in async_migrate_entry
    del new_options[CONF_LOCK_DEFAULT_CODE]
        ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'lock_default_code'

[gjohansson-ST]

@gjohansson-ST For your info; after rebase I got this error from the migration. Might be nothing, but still wanted to let you know. The integration did not load and had to be removed/added to fix the error.

Thanks @niro1987 !! I did not consider the key might not exist. A bugfix PR has been made.

[frenck]

Thanks, @niro1987 👍

../Frenck