Refactor Helm chart to use Kubernetes Secrets for credentials instead of ConfigMaps

[coderabbitai]

Background

Currently, AWS credentials and other sensitive authentication data are stored in Kubernetes ConfigMaps within the Helm chart deployment. For better security practices, these should be stored in Kubernetes Secrets instead.

Proposed approach

1. Isolate credentials from other clp-config fields so their lifecycle can be managed separately
2. Once isolated, move credential values into Kubernetes Secrets for more secure handling

References

• PR feat(helm): Add S3 storage support for archives, streams, and log inputs. #1825: feat(helm): Add S3 storage support for archives, streams, and log inputs. #1825
• Discussion: feat(helm): Add S3 storage support for archives, streams, and log inputs. #1825 (comment)
• Requested by: @junhaoliao