[Decouple] Allow plugin manifest config to define semver compatible OpenSearch plugin and verify if it is installed on the cluster

[manasvinibs]

Description

This PR is an enhancement to the already existing plugin manifest ability to allow defining backend OpenSearch plugin dependencies. As part of decoupling Dashboards with OpenSearch Dashboards plugins and then with OpenSearch, we need a way to establish Dashboards plugin dependency with its counter part.
This PR adds following changes -

• Modifying existing manifest config key requiredOpenSearchPlugins to define list of OpenSearch Plugin object and its version compatibility with that plugin.
• In the first iteration we can define version range in semver format only.
• Compatible version defined in the manifest should be a valid version range.
• Validates if version compatible plugin is installed on the cluster or not.
• In this initial implementation, we are only logging the warning if plugin is not available and does not fail to start.

In the follow-up PRs,

• Add ability to disable Dashboards plugin when its counterpart is not installed on the cluster.
• Export function/API that plugins can extend to decide what they want to do when their OpenSearch counterpart plugin is not installed or is incompatible.

Issues Resolved

#4611

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
  • yarn test:ftr
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov]

Codecov Report

Merging #4612 (bc80e28) into main (754c78d) will increase coverage by 0.02%.
The diff coverage is 95.65%.

@@            Coverage Diff             @@
##             main    #4612      +/-   ##
==========================================
+ Coverage   66.28%   66.31%   +0.02%     
==========================================
  Files        3322     3322              
  Lines       63923    63933      +10     
  Branches    10117    10121       +4     
==========================================
+ Hits        42371    42395      +24     
+ Misses      19061    19050      -11     
+ Partials     2491     2488       -3     

Flag	Coverage Δ
Linux_1	34.84% <ø> (ø)
Linux_2	55.15% <95.65%> (+0.01%)	⬆️
Linux_3	43.38% <0.00%> (-0.01%)	⬇️
Linux_4	35.09% <0.00%> (-0.01%)	⬇️
Windows_1	34.85% <ø> (?)
Windows_2	55.12% <95.65%> (+0.01%)	⬆️
Windows_3	43.38% <0.00%> (?)
Windows_4	35.09% <0.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
src/core/server/plugins/types.ts	100.00% <ø> (ø)
...server/plugins/discovery/plugin_manifest_parser.ts	84.72% <93.75%> (+0.34%)	⬆️
src/core/server/plugins/plugin.ts	100.00% <100.00%> (ø)
src/core/server/plugins/plugins_system.ts	90.52% <100.00%> (+0.20%)	⬆️

... and 3 files with indirect coverage changes

[joshuarrrr]

@kavilla Assigned you as primary reviewer.

[kavilla]

looks good I would just update this one to be the string:string and good to merge.

[AMoo-Miki]

I thought semver was able to convert this to ^2.0.0; no?

[manasvinibs]

I'm doing semver.coerce when reading the version from engine, but this is coming from plugin manifest file and we still expect plugin users to write it in actual semver format. Hence there is a validation check on if the defined version is valid semver range or not.

[AMoo-Miki]

Thanks

[kavilla]

Pretty cool! I think if there is any clean ups or changes to how we want to do it it can be done in a follow-up but I don't see anything right away. So let's let it bake in main for a little.