Use dataclass properties in lutron_caseta discovery

[epenet]

Proposed change

Use dataclass properties in lutron_caseta discovery.

Linked to #60540

⚠️ no longer required since #60561 was merged

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 #
• 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.
• 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.

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.

[probot-home-assistant]

Hey there @swails, @bdraco, mind taking a look at this pull request as it has been labeled with an integration (lutron_caseta) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[epenet]

@bdraco could you help me understand why my changes break the tests?
The tests work fine on my machine - but not in CI.

[bdraco]

@epenet looks like it was missing a await hass.async_block_till_done()

[epenet]

Wow thanks!
Edit: still fails

[bdraco]

nope, still failing

passes locally for me though

[epenet]

Yes it passes for me too

[bdraco]

Not sure one this one. This test needs to be modernized anyways. I'll take a look at cleaning it up when I have a larger time block free.

[bdraco]

I think its failing because of the split CI run.

Likely any change to this integration will probably fail when not run with all the tests

[epenet]

@bdraco you were correct => it passes if we use full CI, but fails on partial CI
This is no longer required since #60561 was merged.

cc @frenck to see if it might be possible to add a label to trigger full CI...

[epenet]

Note to @frenck : it seems that there was a similar issue in xiaomi_miio #60638
Partial tests were failing in Python 3.8, but successful in Python 3.9

Maybe tracking this as an issue is better?

[frenck]

The ciaomi miio case is different and will be fixed in a week or so (as Python 3.8 is being dropped for the 2022 dev)