Before UI plugin resources can be served via Engine (PluginResourceServlet), a plugin must specify "resourcePath" attribute within its descriptor [1], for example:

/usr/share/ovirt-engine/ui-plugins/test.json
{
	"name": "test",
	"url": "/webadmin/webadmin/plugin/test/start.html",
	"resourcePath": "test-resources"
}

After this, URLs such as "/webadmin/webadmin/plugin/test/start.html" can be used to serve resources such as /usr/share/ovirt-engine/ui-plugins/test-resources/start.html

Instead of specifying "resourcePath" in plugin descriptor, we could simply use "<descriptorFileName>-resources" convention which maps to /usr/share/ovirt-engine/ui-plugins/<descriptorFileName>-resources

This is meant to address two issues:
1. ensure each plugin has its own (unique) "resourcePath" value
2. reduce the amount of necessary metadata in plugin descriptor

Migration notes for existing plugins:
- remove "resourcePath" attribute from plugin descriptor (i.e. from test.json)
- ensure plugin resources are put in "<descriptorFileName>-resources" directory (i.e. in test-resources)

This is a breaking change with regard to current behavior/API, introducing this RFE should bump up "apiVersion" as proposed in https://bugzilla.redhat.com/967625

[1] http://www.ovirt.org/Features/UIPlugins#Plugin_descriptor