Add support for occupancy/vacancy groups in Lutron Caseta component

[swails]

Proposed change

This adds support for occupancy groups (Lutron Caseta's version of motion sensors) for which support was recently added to Lutron Caseta system.

This follows updates to pylutron-caseta to add support for these
devices. This code works for me as a custom component in Home Assistant
Core with pylutron-caseta 0.6.0 (currently unreleased).

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

Example entry for configuration.yaml:

# Example configuration.yaml - no change from previous versions
lutron_caseta:
  host: 192.168.1.15
  keyfile: caseta.key
  certfile: caseta.crt
  ca_certs: caseta-bridge.crt

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add documentation about occupancy groups to Lutron caseta home-assistant.io#12466

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

[frenck]

Thank you for your contribution thus far! 🎖 Since this is a significant contribution, we would appreciate you'd added yourself to the list of code owners for this integration. ❤️

Please, add your GitHub username to the manifest.json of this integration.

For more information about "code owners", see: Architecture Decision Record 0008: Code owners.

[swails]

I rebased against the upstream dev branch.

[swails]

The remaining test failure is a result of a new release not being cut yet for pylutron-caseta. I have an issue opened to have that release cut ASAP: gurumitts/pylutron-caseta#43

[MartinHjelmare]

Please ping me here when we're ready to continue.

[swails]

@MartinHjelmare - this is ready to proceed. I removed the breaking changes section of the PR, since those were done in #33144 and no further breaking changes were made here.

The upstream project has published a new release, so we should be ready to move forward.

[MartinHjelmare]

Awesome!