fix(prod/jenkins-beta): read file credentials

[purelind]

No description provided.

[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 title and the diff, it looks like the change is related to fixing a credential issue in the Jenkins configuration for the production environment. Specifically, it changes the way a secret is read by adding a base64 decoding step.

One potential problem is that we don't have enough context to understand why the original code used "${ks3util-config}" instead of "${base64:${ks3util-config}}". If there was a specific reason for this, the change may introduce new problems. It would be good to have more information about why this change was made.

Assuming that the change is necessary, one suggestion for improvement would be to add some documentation or comments to explain the reason for the change. This will make it easier for future maintainers to understand the code and avoid introducing new issues.