Move Misconfiguration Flyout Component From CSP plugin to Security Solution Plugin

[animehart]

Motivation:
In order to implement Misconfiguration/Vulnerability Expandable Flyout, we need to move Misconfiguration Flyout component from CSP plugin into Security Solution Plugin, the reason being is that the new Misconfiguration Expandable Flyout will look similar to Alerts flyout as such we want to reuse the components and functions that already exist there.

In order to call the component from Security Solution, we will pass the hook that calls an API that controls which panel to show from Security solution to CSP plugin.

Definition of Done:

• Misconfiguration Flyout will now reside inside Security Solution Plugin
• Misconfiguration Flyout can be called and rendered by using Expandable Flyout Api Hooks that we passed
• Any Hooks/Constants/Types thats only being used by Misconfiguration Flyout should be moved to Security Solution as well otherwise if its being used by multiple components, we will move it to CSP shared packaged
• Should preserve any previous behaviour such as creating detection alerts, navigating to Benchmark page, etc

Out of Scope:

• Changing the UI of the Misconfiguration/Vulnerability Flyout to look like the Figma Design / Alerts Flyout
• Users able to open Misconfiguration/Vulnerability Flyout from User.name/host.name flyout
• Moving Vulnerabilities Flyout to Security Solution Plugin

Related Epic/Tasks

• https://github.com/elastic/security-team/issues/10143

[elasticmachine]

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)