Add data/data_description translation checks

[epenet]

Proposed change

Based on https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/config-flow, data and data_description are compulsory for every schema field.

Needs:

• Improve renault config-flow translation strings #131706
• Add missing data_description for lamarzocco OptionsFlow #131708
• Add missing data description for solarlog #131712
• Plugwise add missing translation #132239

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.

To help with the load of incoming pull requests:

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

[epenet]

cc @konikvranik, @allenporter for rainbird

[epenet]

cc @zweckj for lamarzocco

[epenet]

cc @cgarwood for fully_kiosk

[epenet]

cc @Ernst79, @dontinelli for solarlog

[epenet]

renault should be handled in #131706

[zweckj]

cc @zweckj for lamarzocco

@epenet should be through #131708

[dontinelli]

cc @Ernst79, @dontinelli for solarlog

PR pending: #131712

[cgarwood]

#131716 for Fully Kiosk

It appears that data descriptions do not show up in the frontend for boolean/checkbox fields.

[epenet]

#131716 for Fully Kiosk

It appears that data descriptions do not show up in the frontend for boolean/checkbox fields.

Interesting... should this be raised as a bug in frontend? or should it be removed from the check here?

[epenet]

@CoMPaTech @bouwew please take look at plugwise issues

[CoMPaTech]

@CoMPaTech @bouwew please take look at plugwise issues

@epenet drafting #132239

[epenet]

@miaucl, @tr4nt0r there are new violations for bring, could you take a look?

=========================== short test summary info ============================
ERROR tests/components/bring/test_init.py::test_init_failure[BringAuthException-ConfigEntryState.SETUP_ERROR] - Failed: Translation not found for bring: `config.step.reauth_confirm.data_description.email`. Please add to homeassistant/components/bring/strings.json
ERROR tests/components/bring/test_config_flow.py::test_flow_user_init_data_already_configured - Failed: Translation not found for bring: `config.step.user.data_description.email`. Please add to homeassistant/components/bring/strings.json
ERROR tests/components/bring/test_config_flow.py::test_flow_reauth - Failed: Translation not found for bring: `config.step.reauth_confirm.data_description.email`. Please add to homeassistant/components/bring/strings.json
ERROR tests/components/bring/test_config_flow.py::test_flow_reauth_unique_id_mismatch - Failed: Translation not found for bring: `config.step.reauth_confirm.data_description.email`. Please add to homeassistant/components/bring/strings.json

[epenet]

@arturpragacz there are new violations for onkyo, could you take a look?

=========================== short test summary info ============================
ERROR tests/components/onkyo/test_config_flow.py::test_options_flow - Failed: Translation not found for onkyo: `options.step.init.data.TV`. Please add to homeassistant/components/onkyo/strings.json

[arturpragacz]

The input source names in Onkyo should not be translated, as they are international by nature. They should also not have any individual descriptions.

[epenet]

The input source names in Onkyo should not be translated, as they are international by nature. They should also not have any individual descriptions.

I've added "ignore_translations" for this use case

[frenck]

Thanks, @epenet 👍

../Frenck