Cloudformation: Investigate if cloudbeat-root is needed in single account

[moukoublen]

The role cloudbeat-root seems to be used only in AWSOrg functionality and thus not needed in single account cloudformation script.

Single account cloudformation deploys the role ElasticAgentRole (with a unique name) that contains the necessary policy (SecurityAudit) that is then referenced into ElasticAgentInstanceProfile which is used into the EC2 instance which seems to be enough for the single account.

We should verify that cloudbeat-root is not actually used in single account cspm (aws - cloudformation) deployments and if it's not we should remove it from single account cloudformation yaml.