Upgrade lakeside to 0.13

[nkgilley]

Breaking change

Proposed change

• Upgrade lakeside dependency to fix issues with latest protobuf package.
• nkgilley/python-lakeside@c3f2fef...nkgilley:python-lakeside:0.13

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 Eufy integration no longer working after upgrading supervisor to 2023.04.0 #91614
• 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 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.

[MartinHjelmare]

I just noticed that your fork is still connected to the archived repo. It's nice to disconnect it to make it easier to compare releases etc. Maybe it's under way at github, if you asked them already?

[MartinHjelmare]

I added a github commit diff link to the PR description.

[MartinHjelmare]

Thanks!

[nkgilley]

I just noticed that your fork is still connected to the archived repo. It's nice to disconnect it to make it easier to compare releases etc. Maybe it's under way at github, if you asked them already?

I'll request the disconnect now.