Handle no data error in Electricity Maps config flow

[jpbede]

Proposed change

The Electricity Maps can respond with {"status": "no-data", ...}, which means that no data is available for the selected region. The upstream lib raises a ElectricityMapsNoDataError in this case. This PR deals with this in the config flow.

Also remove api_ratelimit from strings.json, which is not needed anymore.

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.

[home-assistant]

Hey there @VIKTORVAV99, mind taking a look at this pull request as it has been labeled with an integration (co2signal) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of co2signal can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign co2signal Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[VIKTORVAV99]

Just one tiny suggestion otherwise things look good from my side.

[lellky]

In the PR description it says "status=no-data" but in the code it says "no_data": "No data is provided for the location you have selected.". Do you mean in the PR description "status=no_data"?

[jpbede]

No that is right, the PR is confusing yes, the API returns {"status": "no-data", ...}, the lib throws than a error. This PR deals with this error.

[lellky]

Looks good to me!

[farmio]

LGTM 👍