Expose package info to NP plugins

[mshustov]

Summary

Closes: #45262

Provides packageInfo to NP plugins via PluginInitializerContext on both client and server

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• [ ] This was checked for cross-browser compatibility, including a check against IE11
• [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• [ ] Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• [ ] This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

Dev Docs

Kibana package information provided to the plugins in constructor as a part of PluginInitializerContext

class MyPlugin {
  constructor(context: PluginInitializerContext){
    const isDitribution = context.env.packageInfo.dist;
  }
}

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: ce9ea0b

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: cc83a04

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 8788a5a

[lizozom]

@ppisljar app-arch team is added as mandatory reviewers every time changes are made to /src/plugins/data/server.

Should our team be responsible only for /src/plugins/data/public and maybe /src/plugins/data/common?

[ppisljar]

@lizozom we own the whole plugin (the only thing in server is the search service for the moment, but index patterns expose an endpoint as well)

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: 8788a5a