Bump pysnmp-lextudio to version 6.0.11

[lextm]

Breaking change

Proposed change

As reported in #113457, a bug in pysnmp-lextudio prevents device tracker from working properly for many known SNMP devices (but a few might continue to work).

pysnmp-lextudio version 6.0.11 contains the fix.

While we are able to add new test cases to pysnmp package to confirm the bugfix, we are not yet familiar with home assistant setup to perform thorough testing.

changes: lextudio/pysnmp@v6.0.9...v6.0.11

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 SNMP device tracker broken in 2024.3.1 #113457
• 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.

[bdraco]

Thanks @lextm

[bdraco]

Tested on prod. All good

[lextm]

@bdraco Thanks for accepting this.

BTW, what's your recommendation if we want to test out the latest dev branch to ensure everything works, not just unit testing? Should we set up Home Assistant differently from a method in https://www.home-assistant.io/installation/? Right now we are using a HA OS VM running on VirtualBox/macOS, but that does not seem to allow us to test the latest dev branch.

[bdraco]

If it's a container, I usually install nightly and swap out the code inside with something like

docker exec -it homeassistant /bin/bash

cd /usr/src
apk add autoconf automake libtool m4 gmp-dev mpfr-dev mpc1-dev gcc musl-dev openssl-dev libffi-dev ffmpeg-dev rust cargo zlib-dev jpeg-dev g++ make
git clone https://github.com/bdraco/home-assistant
mv homeassistant/ homeassistant.orig
mv home-assistant/ homeassistant
cd homeassistant
git checkout -t origin/integration
pip3 install --upgrade maturin
pip3 install --upgrade -r requirements.txt  --find-links=$WHEELS_LINKS -c ./homeassistant/package_constraints.txt
python3 -m script.translations develop --all

[lextm]

@bdraco Thank you very much. We will give that a try.