New optional field: ui_frameworks

Goal: Allow the creation of plugin versions that are targeted only to specific UI Frameworks.

• Each plugin version can define an array of supported UI Frameworks.
• The default supported UI Framework is called "native".
• At the time of the 0.61.0 release, the available UI Frameworks are: ["native", "quickbrick"].
• If this field is supplied in the manifest, the plugin version will be saved with the default UI Framework.
• List of available UI Frameworks is taken from Zapp's API.

Manifest example I: A plugin supported both in QuickBrick and in Native, e.g. a datasource plugin

{
 "platform": "android",
  "author_name": "Me",
  "name": "My plugin",
  "identifier": "my_plugin",
   ... // etc.
  "ui_frameworks": ["native", "quickbrick"]
}

Manifest example II: A plugin that should be added only to mobile QuickBrick apps - notice the targets. e.g. a view component

{
 "platform": "android",
  "author_name": "Me",
  "name": "My plugin",
  "identifier": "my_plugin",
   ... // etc.
  "targets": ["mobile"],
  "ui_frameworks": ["quickbrick"]
}

What should I expect from this field in the future?

• Plugins will be filtered for each app version according to the UI Frameworks, e.g.: Only plugins tagged with a "quickbrick" UI Framework will be shown in the Plugin Gallery when working on an App Version using QuickBrick. TBD.