[Fleet] Proposal: invert dependency between osquery and infra plugins

[hop-dev]

Currently the infra plugin has a dependency on the osquery plugin. This is preventing the fleet plugin from using the infra plugin as a cyclical dependency is created by osquery depending on fleet. The dependency cycle looks like this:

fleet --required-> infra --optional-> osquery --optional-> fleet

There are a few options to solving this, @joshdover has looked at a lot of possibilities in this comment.

We are proposing inverting the ifra -> osquery dependency as there is already logic in infra for when osquery is not enabled meaning they already reasonably loosely coupled.

Josh says it best on how we would invert the dependency:

infra would need to expose an API like registerOsQueryActionComponent and have the osquery plugin call this on the infra plugin.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[hop-dev]

@elastic/logs-metrics-ui and @elastic/security-asset-management I believe you manage infra and osquery respectively?

[joshdover]

Let's continue the discussion #126578