Prevent plugins from breaking after minor Kibana updates

[Dom-nik]

Kibana version: 5.0.x

Describe the feature:
The problem I'm describing is rather predictable/obvious, but quite frustrating.
The release cycle for Kibana is very fast and the plugins that worked fine for Kibana 5.0.0 break (to be precise: get turned off because of version discrepancy) after an upgrade to 5.0.1, even though it seems that such small upgrade (bugfixes mostly) shouldn't break them.
Please implement different version checking, so that minor updates don't break plugins.

Extra:
There are two workarounds I found, but they are manual and shouldn't be end users' problem. It seems that the second one can be a permanent solution, if it gets adopted by plugin developers:

1. Do as follows:
   a) download your plugin,
   b) unzip it into $KIBANA_HOME/plugins,
   c) change "version" in the package.json file to match your Kibana version, e.g.: "version": "5.0.1"
   This requires changing after each update.

2. Do as in 1, but change "version" to "kibana" ("version": "kibana"), the same way it is set up in core plugins ($KIBANA_HOME/src/core_plugins), as proposed by one of the plugin developers: Missing "version" in package.json JuanCarniglia/area3d_vis#1 - it seems that whis will work for all further updates, but is less safe.

Please refer to: https://discuss.elastic.co/t/plugins-break-after-upgrade-5-0-0-5-0-1/66401

[thomasneirynck]

see also #9019 for additional discussion on this topic.

[epixa]

I'm going to close this as a duplicate of #9019

@Dom-nik If you haven't seen it already, I left a comment in the other issue that describes the reason for the hard requirement on Kibana version in plugins. Basically: some patch versions will break plugins, so while it is convenient to not fix the kibana version on plugins, it's dangerous for production Kibana installs to run plugins that aren't explicitly tested on the current version.