[cloud connected mode] Manage autoOps agents in a native manner in ECK

[Kushmaro]

Background
As part of our Elastic Cloud Connected mode, we'd like ECK users and customers to be able to deploy the AutoOps agent as an ECK managed resource (rather just a kubernetes deployment )

Whether it would be a CR or just a property in the existing ES CR, is still up for debate.
This is a placeholder issue until all requirements are jointly hashed out with the AutoOps team

Questions to clarify
:: Configuration of a users Elastic Cloud account

• Should this be per namespace? for the entire cluster? either or option?
• Do we see a use case where 1 k8s cluster uses multiple cloud connected autoops instance? (i.e orgs)
• Same goes for region / cloud provider selection
• Are there any other user settings that are relevant?
• • Which clusters to monitor / which namespaces / at what level should this be?

cc @ori-shafir