FST plugin should expose (DAW-automatable) parameters for MIDI CC, like in VST 3

[attilammagyar]

MIDI CC in the VST 3 standard is implemented by exposing virtual parameters which are automatically assigned to MIDI CC events, which has the side-effect that those parameters can also be conveniently controlled and automated in various ways using the DAW's automation lanes. The latter part is actually a nice little feature, which probably could, and if so, should be implemented in the FST plugin version as well. (See issue #6.) Feature parity is a good thing.

Motivation: let's say the plugin exposed all its parameters. But then what should happen if a parameter has an automation track in the DAW and at the same time, is assigned to a controller within the plugin? This ambiguity could be resolved by introducing a new controller named Host, which would mean that parameters which have this controller assigned to them, would be automated by the DAW. But this seems redundant, because DAWs can already send automated MIDI CC events to the plugin, and the plugin already supports automation by MIDI CC, so the basic functionality already exists, without a single line of new code. ("The best code is no code at all.") However, being able to use the automation track vs. having to edit automations in the MIDI editor are sometimes very different in terms of convenience, hence the issue.