Adds new integration [SpanPanel/Span]

[cayossarian]

Checklist

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

Links

Link to current release: https://github.com/SpanPanel/SpanHACS/releases/tag/0.0.11 Link to successful HACS action (without the ignore key): https://github.com/SpanPanel/Span/actions/runs/9440584504/job/26000115546 Link to successful hassfest action (if integration): https://github.com/SpanPanel/Span/actions/runs/9440584504/job/26000115367

[cayossarian]

SPAN vendor product manager is in favor for the repository change. This repository is many commits ahead of the upstream current default Span integration. I believe the upstream repository is abandoned as critical (crash) pull requests are not being processed for some time. The upstream does not allow writes from contributors. The subject of this pull request is now part of an Github organization with code owners/members who previously contributed fixes for previous forks, modulo the upstream personal repository owner who has not responded to his invite as of yet.

[countrock]

Can someone take a look and approve this?

[starsoccer]

+1 to this

[wez]

Would love to see this get merged!

[starsoccer]

+1

[cayossarian]

Add link to remove currently abandoned default repository

[gdgib]

The current repo isn't abandoned. I just didn't get any notifications about issues or PRs in months, and it was working locally, so there wasn't any apparent need for changes.

1. I've moved the current repo to https://github.com/haext so users will see an update NOW with all the features from the fork.
2. @cayossarian is already invited to join the team for that as a maintainer.
3. I'd like to work with @cayossarian in https://github.com/haext/span/issues/55 to decide what comes next, because WOW was it not good to find out I've not been notified of months of excellent work, and people having problems I could have fixed.

[cayossarian]

@gdgib merged repositoies with SpanPanel Org so this issue is no longer relevant.

[gdgib]

Please see https://github.com/hacs/default/pull/3012 where we'd like to update the repository, so that we're not relying on github redirects. In the meantime, all users will already see current code through HACS either way.