Add per script partial settings

[tbd-vam]

Axis settings are currently stored in 'MultiFunPlayer.config.json'. It would be useful if they were saved on a script-by-script basis, instead. Parameters like invert, scale, offset or linked axes are unique to the script, that's currently playing.

Those parameters could be stored in a central database or alternatively along with the scripts, e.g.:
[script path]\[script name].[axis].mfpsettings.json

I started mocking up a plugin to do this but soon hit a wall when I realized both the SettingsMessage record as well as AxisSettings and PropertyManager classes are internal.

[Yoooi0]

Similar to #114 just per script. This could be implemented at the same time as a separate button.

Depending on which MFP version you use the plugin should be pretty easy. Tho not ideal because it requires specific string for reading and writing the property values.

Assuming latest:

• Add a shortcut action for saving partial settings (or UI button)
  • On click, read desired properties with "ReadProperty", for example
    var offset = ReadProperty<DeviceAxis, double>("Axis::ScriptOffset", DeviceAxis.Parse("L0"));
  • Save to partial settings json
• Handle "ScriptChangedMessage"
  • Read partial settings if they exists
  • Apply each with "InvokeAction", for example
    InvokeAction<DeviceAxis, double>("Axis::ScriptOffset::Set", DeviceAxis.Parse("L0"), offset);

[tbd-vam]

I got the fundamentals working, but only for offset and scale.
Apparently, there are no property getters for InvertValue, LinkAxis, LinkPriority and others, even though there are setters.
There's also a small inconsistency in the naming of the offset getter/setter:

• get: "Axis::Offset"
• set: "Axis::ScriptOffset::Set"

[Yoooi0]

Yes, I don't remember why there were a lot of missing properties in 1.31, I must have forgot to add them before release.
In 1.32 I added all missing properties, so every action should have a corresponding property.