Currently the DSPO requires that for external connections the DSPA be given an k8s secret and the `keys` in which the required confidential data is provided. Once submitted the DSPO will manage its own k8s secret (a duplicate). This seems unnecessary given (1) the secret will never be expected to change and (2) the structure of the secret is always the same (e.g. for object storage the keys will always contain a Secret Access Key and an ID).

Acceptance Criteria:
The DSPA should instead take only a `secret name` for a k8s secret, always assume a specific set of Keys for object store/db connections, assume the secret will always be in the same name space. And simply leverage the secret directly and not create a new secret to manage. This one secret should be able to be used for both db/s3 connections.