[Security Solution] Revert security_solution_common package which is unnecessary

[logeekal]

Summary

This PR reverts #189633.

Background

PR : #189633 had created a package security_solution_common so that security components can be easily used in Discover plugins.

But because of recent direction change, I have decided to revert that change which mainly moved flyout code to the security_solution_common package.

Most of the changes that you will see will be path changes replacing security_solution_common.

TL;DR

security_solution_common is being removed as the reason it was created does not exists any more.

[logeekal]

/ci

[elasticmachine]

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

[logeekal]

/ci

[tomsonpl]

Defend Workflows Code changes LGTM 👍

[seanrathier]

LGTM

[PhilippeOberti]

left a few very minor comments

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: 86534ec
• Storybooks Preview

Failed CI Steps

• Post-Build

Metrics [docs]

‼️ ERROR: no builds found for mergeBase sha [b4ed7a1]

History

• 💔 Build #247108 failed ed657de
• 💔 Build #247036 failed 2e73768
• 💔 Build #246979 failed 5a35fbc

[davismcphee]

Code-only review, Data Discovery changes LGTM 👍 Just to confirm, are you removing security-solution-common because you're no longer intending to extract the components and instead use discover_shared for IoC?

[logeekal]

Code-only review, Data Discovery changes LGTM 👍 Just to confirm, are you removing security-solution-common because you're no longer intending to extract the components and instead use discover_shared for IoC?

Thanks @davismcphee . To answer your question, Yes, exactly. In current state security-solution-common does not make sense as it was partial decomposition so I reverted it in favour of discover_shared.