Release 10.1.2 broke S3 existingSecret support

[DaDummy]

After upgrading to 10.1.2 an existing secret is no longer correctly recognized, which in turn causes the seeder to fail with the following error:

rake aborted!
ArgumentError: Missing required arguments: aws_access_key_id, aws_secret_access_key (ArgumentError)

          raise ArgumentError, "Missing required arguments: #{missing.join(', ')}"

The issue appears to be, that the secretKeys configured in values.yaml are no longer correctly applied to the resulting seeder job's definition.

Instead of

        envFrom:
[...]
        - secretRef:
            name: (existing secret)

the following definition is expected here:

        env:
        - name: (target environment var name)
          valueFrom:
            secretKeyRef:
              key: (existing secret key)
              name: (existing secret)

[famfop]

I was just coming back to trying s3 with custom secrets and I am having the same error on a fresh install. Note that in #190 it was mentioned to be supposed to be fixed in 10.1.2 but it seems it is not yet a complete solution (or maybe it broke something else?).