Update vesync to use new fan entity model

[bdraco]

Requires #45407

Proposed change

Update vesync to use new fan entity model

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

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

This pull request needs to be manually signed off by @home-assistant/core before it can get merged.
_{^{(message by ReviewEnforcer)}}

[probot-home-assistant]

Hey there @markperdue, @webdjoe, @TheGardenMonkey, mind taking a look at this pull request as its been labeled with an integration (vesync) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[balloob]

Should there be a FAN_MODE_NONE so that users can disable a preset mode ?

[bdraco]

I'm trying to think about how I would use it.

I'm thinking I would use it like:

from Auto -> Medium Speed or Auto -> Off and wouldn't do Auto -> None -> Medium

[bdraco]

I'll do some testing with the frontend PR to make sure that is actually how I would use it with the demo fan.

[bdraco]

If the device still reports the fan level in Auto mode, maybe it makes sense to add Manual (suggested as None).

If the device doesn't report the fan level in auto mode then it probably is fine as is.

[bdraco]

I ordered a LV-PUR131S for testing and will adjust later if needed

[TheGardenMonkey]

I ordered a LV-PUR131S for testing and will adjust later if needed

I am available to test this when you feel it is ready as well. I have 3 of these.

[bdraco]

If you could give the latest dev a try along with latest frontend with home-assistant/frontend#8216 and provide feedback, that would be most excellent.