[Cloud Security Posture] Add cloud connector support for Asset Discovery Integration

[Omolola-Akinleye]

Proposed commit message

In This PR, we are adding cloud connector support for Asset Discovery Integration and enable Agentless agent to use the trusted Cloud Connector authorization flow. We are add configuration Cloud Connector configuration settings such as

• External ID field - secret field used to assume role in Cloudbeat

• Cloud Formation Template Url - link will create a cloud formatiion stack that generates Role ARN and External Id.

The Role ARN field and External Id fields will be used to assume the role and establish trust between Elastic and AWS.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Screenshots

[moukoublen]

We'd also need the supports_cloud_connectors
on this file:
packages/cloud_asset_inventory/data_stream/asset_inventory/agent/stream/aws.yml.hbs

like this

      account_type: {{aws.account_type}}
      {{#if aws.supports_cloud_connectors}}
      supports_cloud_connectors: {{aws.supports_cloud_connectors}}
      {{/if}}

this is how the aws.supports_cloud_connectors from the manifest is propagated to the configuration that arrives to the cloudbeat.

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: af405a2

Failed CI Steps

• Check integrations cloud_asset_inventory

History

• 💔 Build #26584 failed d7a9101
• 💔 Build #26338 failed 1430748
• 💔 Build #26337 failed ecce479

cc @Omolola-Akinleye