feat: Speaker Api: Part Two

[MS-crew]

Description

Describe the changes

• Added automatic controller ID assignment via GetNextFreeControllerId()
• Added object pooling system (Pool, Rent(), ReturnToPool(), PlayFromPool()) for improved server performance
• Added PlaybackProgress propertie
• Fixed Null Referance Exception for TargetPlayers and Predicate in SendPacket
• Magic things change to consts
• Added Fade Effect
• Added Time Based Events
• Added Track Queue
• Added Static Events For Global non-object-oriented Usages
• Added AudioPlaybackOptions struct for more clean Play method and not breaking things in future
• Added PreferredId logic in Rent for avoiding unnecessary network sync wait
• Added onComplete Action for FadeVolume method
• Fixed memory leak for events in ReturnToPool
• Added RestartTrack method
• Open api supporting all IPcmSources
• Add URL wav source
• Add Player Stream Source

What is the current behavior? (You can also link to an open issue here)
Tittle

What is the new behavior? (if this is a feature change)
Read

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:

Example Audio Time Event :

speaker.AddTimeEvent(timeInSeconds: 19, action: () => Map.TurnOffAllLights(99999999));
speaker.AddTimeEvent(timeInSeconds: 40, action: () => { Map.TurnOffAllLights(0); Map.Broadcast(new ("In The Night!")); });

timebased.mp4

Example Fadings :

fadein.mp4

2026-03-21_14-48-20.mp4

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentations

Submission checklist

• I have checked the project can be compiled
• I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

• I have checked no IL patching errors in the console

Other

• Still requires more testing

[Someone-193]

if we're gonna test error handling for the speaker api, could you at least check each type of error and make sure it doesnt spam the log if an issue happens then let us know you've tested all the errors?

[Someone-193]

Considering how much effort you've put into this, I'm just gonna trust that you've tested every feature lol

[Someone-193]

https://tenor.com/view/fire-writing-holy-holy-writing-fire-writing-gif-12998741943022322982