Bump vilfo-api-client to 0.5.0

[ManneW]

Proposed change

Update vilfo-api-client dependency to latest version. By using the latest version of vilfo-api-client, issues with conflicting package versions should hopefully be resolved and the work with pull request #113245 should be possible to progress.

The update to the vilfo-api-client package is documented here.

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:
• This PR is related to issue: Bump plugwise to v0.37.1 #113245
• 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 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.

[bouwew]

@ManneW Please run python3 -m script.gen_requirements_all to update the vilfo-backend version nr. in the HA requirements files.

Or update the HA files requirements_all.txt and requirements_test_all.txt by hand :)

[edenhaus]

Test failure unrelated