Bump pwmled to v1.6.6

[soldag]

Proposed change

Mainly improves performance of transitions and fixes configuring the frequency when using a gpio driver.

soldag/python-pwmled@v1.5.3...v1.6.6

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)
• 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 rpi_gpio_pwm error after upgrade to 0.117.1 #42650
• 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
• 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[springstan]

LGTM 👍

[soldag]

Ready to merge from my side. CI just failed because GitHub was not available at that time and I can't rerun it.

[springstan]

@soldag does this version bump solve #42650?

[soldag]

@springstan Fixed it in v1.6.6 of the lib and changed this MR accordingly. Thanks for referencing the issue. I wasn't aware of it.

[springstan]

Of course, fyi you can add yourself as codeowner of this integration so you are automatically tagged when an issue or PR comes up regarding this integration.

[springstan]

Tagging this for the next patch release since it fixes an issue that came up in 0.117.