💥 Reduce allocations in VST3 audio sockets

We do this by using this new `MessageReference<T>` type to avoid copying
our `YaAudioProcessor::Process` struct and the contained `YaProcessData`
object. This is only part of the work, but this redesign lets us keep
the these objects alive on both the plugin and the host side. On the
plugin side, we'll simply serialize the data from the referred to object
without copying it. On the Wine side, we'll write the data to a
persistent thread local object, and then reassign the
`MessageReference<T>` to point to that object. This lets us serialize
'references', thus avoiding potentially expensive allocations. With
these last few changes alone VST3 plugins are already at the same
performance level as our optimized VST2 plugin groups.

CHANGELOG.md

@@ -19,6 +19,12 @@ Versioning](https://semver.org/spec/v2.0.0.html).
   this can significantly reduce the overhead of bridging VST3 plugins under
   those hosts.
 
+### Changed
+
+- Redesigned the VST3 audio socket handling to be able to reuse the process data
+  objects on both sides. This greatly reduces the overhead of our VST3 bridging
+  by getting rid of all memory allocations during audio processing.
+
 ## [3.2.0] - 2021-05-03
 
 ### Added