Generate translation in vscode taks: Code Coverage

[Thomas55555]

Breaking change

Proposed change

Sometimes I forget to generate the translations before running a code coverage report and the tests fail, and spending time on finding the cause of it. With this PR, the translation for the integration is done before. If the integration has no strings.json the generating of the translation fails and just the tests run.

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

To help with the load of incoming pull requests:

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

[gjohansson-ST]

Can't we just use dependsOn to run the translations development beforehand. It's pretty fast so no need to develop perhaps just for the individual integration.

[timmo001]

This should probably be a dependsOn as @gjohansson-ST said. Not sure this make sense to run every time

[Thomas55555]

The problem is, this works only if Compile English translations for a given integration is successful. Bute for integrations without translations this doesn't work.