Platform/wasm browser

[KieranFoot]

Working on fixing Blazor WASM support.

Todo list:

• MiniAudioEngine.DataCallback cannot be used as-is in WASM.
• Synchronous Stream IO not supported in the browser.
• Monitor.Wait() not supported on browser. (Used manually and in Task.Wait())
• System.Security.Cryptography.ECDsa not supported in the browser.
• System.Security.Cryptography.AES not supported in the browser.
• Browser file stream cannot use Seek() and must be wrapped in a MemoryStream or another fix found.

[github-actions]

Welcome to SoundFlow repository! We appreciate you taking the time to contribute.

We're excited to review your pull request and look forward to collaborating with you. Please let us know if you have any questions or need any assistance.

Thank you for your contribution!

[KieranFoot]

I have successfully found all code that is not compatible with the browser and annotated it as such.

Unfortunately, to finish WASM compatibility, a considerable amount of code will have to be re-written to use asynchronous stream IO exclusively and to take out all uses of Task.Wait() and Monitor.Wait().

Also, the frameworks implementations of Aes and ECDsa are not supported in the browser and will need to made to use implementations from the BouncyCastle.Cryptography library instead.

[KieranFoot]

Since many implementations of ISoundDataProvider read data from a stream in their constructors, I propose moving the constructor code to an Initialize() and / or InitializeAsync() method allowing for the inner stream IO to be fully asynchronous when required.

Also, I propose the addition of ReadBytesAsync() for use in the browser.