fix(prod/jenkins): correct read file credentials

[purelind]

use base64 to correct read file credentials.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from purelind, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• apps/prod/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the pull request title and description, the key change is that the secretBytes field in the values-JCasC.yaml file for the ks3util-config has been updated to use the base64 function to correctly read the file credentials.

One potential problem that I see is that it's not clear whether the ks3util-conf value is already base64 encoded or not. If it's already encoded, then applying the base64 function again will result in an invalid encoding which may cause issues.

To fix this, the contributor should ensure that the ks3util-config value is not already base64 encoded before applying the base64 function. They could do this by decoding the value first (if it is already encoded) before applying the base64 function.

Another suggestion would be to provide more context in the pull request description to explain why this change is necessary and what problems it solves. This will help reviewers understand the reasoning behind the change and ensure that it aligns with the project's goals.