Story

As a user of cluster logging on HyperShift based ROSA,

I want to be able to create a forwarder spec with multiple cloudwatch inputs and outputs,

So that logs are forwarded to each output via STS authentication.

Acceptance Criteria

• Verify a single output can be forwarded to Cloudwatch using STS
• Verify multiple inputs/outputs can be forwarded to CW using STS
• Verify vector config is using unique static sts credentials per CW sink, rather than env vars
• Verify functional and e2e tests pass without regression

Notes

• First going to verify a single output, most likely of type 'infra', using STS on my dev account, using the currently provided test cluster
• The secret will be the name of the cluster, so need to verify location of token is working as a path of secret.   
• Only role_arn is required in the secret (unchanged).   Since we are setting the token path based on the secret name, there is no need for the user to specify token path in the secret.