Create Technical Profile for Testing Purposes

Before we start working on implementing deployment, we need a standardized technical profile in the correct location (created in #65 (closed)) to work from. This should include a minimal number of packages and follow all best practices as defined in https://repo1.dso.mil/big-bang/customers/template. This will be our standard profile to work from the entire epic.

The initial repo MR created a "default-profile" folder which can be used for this purpose -> big-bang/customers/technical-profiles!15 (merged). It currently deploys the default values.yaml from Big Bang with no modifications except registry credentials and the Big Bang dev TLS cert.

The secrets.enc.yaml encrypted secrets file has a single developer's registry credentials and is encrypted using a local GPG key.

Acceptance Criteria

• Update the credentials in the secret to be a generic or bot account so that it can be used by the whole team
• Make the encyption key available to the team by uploading it to a shared secret store like KMS
• Validate the default-profile can be deployed manually into a k3d cluster