Bump aiosendspin to 3.0

[balloob]

Summary

This PR shows a preview of the changes needed to adapt to breaking changes in aiosendspin 2.0 and 3.0.

The changes are due to breaking changes in Sendspin/aiosendspin#112 and Sendspin/aiosendspin#115 that we're testing out:

• start_server now accepts multiple addresses to listen on for discovery
• Event listener callbacks changed from async (Coroutine) to synchronous
• start_server() API changed from advertise_host: str to advertise_addresses: list[str] | None

Changes made

provider.py:

• Changed event_cb() from async to sync
• Extracted async logic into _handle_client_added() and _handle_client_removed() helper methods scheduled via self.mass.create_task()

player.py:

• Changed event_cb() from async to sync (no async operations needed)
• Changed group_event_cb() from async to sync
• Extracted async group.stop() logic into _handle_member_removed() helper method scheduled via self.mass.create_task()
• Changed advertise_host parameter to advertise_addresses list

[maximmaxim345]

Have some weird syncing issues with aiosendspin version 3.0.0. After grouping and ungrouping players (in my case cast and web players) a couple of times, some players start playing out of sync or sometimes don't play at all.

Will investigate more into why this happens.

Edit: underlying issue was probably already existing before 3.0.0, but the changed logic in determine_optimal_format (Sendspin/aiosendspin#129) "activated" it.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[maximmaxim345]

Turns out the issue with out of sync players wasn't due this bump to aiosendspin 3.0.0.
The main issue was a bug in sendspin-js, which caused out of sync playback after stream restarts. Its now fixed in sendspin-js version 1.0.1