Adds new integration [Adefx/ha-custom-heartbeat]

[Adefx]

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/Adefx/ha-custom-heartbeat/releases/tag/v1.0.2
Link to successful HACS action (without the ignore key): https://github.com/Adefx/ha-custom-heartbeat/actions/runs/24960053388
Link to successful hassfest action (if integration): https://github.com/Adefx/ha-custom-heartbeat/actions/runs/24960053391

Hello HACS team! 👋

This PR adds a new integration to the default HACS store: Custom Heartbeat.

Description of the integration:
It is a lightweight, 100% UI-based (Config Flow) integration that sends a regular background life signal (HTTP GET request) to external monitoring services like Uptime Kuma, Healthchecks.io, or UptimeRobot.

Why it adds value to the community:
Currently, to ping a push-monitor like Uptime Kuma, Home Assistant users must rely on custom rest_command or sensor rest YAML configurations combined with time-pattern automations. This integration solves this common need by offering a native, plug-and-play, and fully UI-configurable solution.

Key technical details:

• Domain: heartbeat_push
• Config Flow: Fully supported (No YAML required).
• Performance: 100% async. It uses Home Assistant's native async_get_clientsession (aiohttp) to ensure it does not block the event loop.
• Compliance: Repository structure complies with HACS requirements. All GitHub Actions (HACS & Hassfest) are passing successfully.
• Brand icon is handled natively via the HA Core brand folder structure.

Thank you for your time and for maintaining HACS! Let me know if any changes are required.

[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