Adds new integration [moryoav/ha-gwm-ev]

[moryoav]

Checklist

• I've read the publishing documentation.
• I've added the HACS action to my repository.
• (For integrations only) I've added the hassfest action to my repository.
• The actions are passing without any disabled checks in my repository.
• I've added a link to the action run on my repository below in the links section.
• I've created a new release of the repository after the validation actions were run successfully.

Links

Link to current release: https://github.com/moryoav/ha-gwm-ev/releases/tag/v0.17.2
Link to successful HACS action (without the ignore key): https://github.com/moryoav/ha-gwm-ev/actions/runs/34122653340
Link to successful hassfest action (if integration): https://github.com/moryoav/ha-gwm-ev/actions/runs/34122653341

Description

I maintain both repositories and would like to add moryoav/ha-gwm-ev as the maintained successor to moryoav/ha-gwm_ora.

My original integration was accepted in #8714. Its listed URL now redirects to moryoav/ha-gwm, which I have archived. I continue development in moryoav/ha-gwm-ev, a separate repository for the current GWM integration.

I kept the gwm_ora Home Assistant domain. The current integration connects directly to GWM cloud services and requires a fresh sign-in with a dedicated account. This listing change does not migrate existing credentials or configuration entries.

I included the required country metadata and local brand assets in v0.17.2. All nine HACS checks and Hassfest passed before I published that release. The full Python suite also passed 1,356 tests: https://github.com/moryoav/ha-gwm-ev/actions/runs/34122372172.

I added only the new repository entry and kept the list sorted. I requested removal of the archived listing separately in hacs/integration#5528.

[hacs-bot]

Your branch seems out of date. Please update your branch with the latest changes from the base branch.

[hacs-bot]

Thank you for submitting your repository to HACS (Home Assistant Community Store).

Your submission is in the review queue:
Your repository is waiting to be reviewed and included in HACS.

You can view the current queue here. Pull requests are processed in the order they were created, oldest first.

What to avoid during review:
To help reviewers work efficiently, don't do the following:

• Comment on the pull request - The reviewer will contact you when they have feedback or questions.
• Open a new pull request - This won't speed up the process and creates duplicate work.
• Ask followers to comment on the pull request - This won't speed up the process and may delay your review.
• Merge in the default branch - Only do this if a maintainer asks you to resolve a merge conflict.

If you need to make changes:
You can continue updating your repository while waiting for review. Changes to your repository will be reflected when the reviewer examines it. Only comment on the pull request if you need to withdraw your submission or have critical information for reviewers.

About draft pull requests:
Draft pull requests aren't included in the review queue. Your pull request may be marked as draft by a reviewer if issues need to be addressed. Once you've resolved all issues, mark it as ready for review to re-enter the queue.

What happens next:
Once a reviewer examines your submission, they'll either:

• Approve and merge your pull request if everything meets the requirements
• Request changes or ask questions if adjustments are needed