Create single sound pool functioning across multiple backends

[cartertemm]

A sound_pool and it's functions rely heavily on instances of the sound class to do their dirtywork.
Aside from that, very little changes. slot reservations, function names, function signatures, etc etc.
With the status quo, we're writing custom pools for each and every backend. This seems like far too much unnecessary code.
If we leave the responsibility of conversions to each sound class, we could have a single sound pool that remains static regardless of internals. This would alleviate the need for

• Writing extra code
• Reinventing the wheel time and time again
• Confusion

As long as the sound class, and I can't stress this enough, maintains our ranges and function signatures/operations in verbatim this would work. We shouldn't be dealing with a bunch of contrast here anyway.

[brightening-eyes]

we can have an abstract class for sound objects, and instanciate the provided backend and call through provided functions

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed due to inactivity.

[pauliyobo]

Way to talk about issue resurrection. Anyway, reopening this issue, since it hasn't been fixed yet.