Change job's user ID to fix SCC violation

[ruivieira]

Refers to RHOAIENG-13846.

The pod is trying to run with a runAsUser UID of 1001030000, which is outside the allowed UID ranges specified by the Security Context Constraints available to the pod's service account.

This PR sets it to a UID within the allowed range [1000840000, 1000849999].

[github-actions]

PR image build and manifest generation completed successfully!

📦 PR image: quay.io/trustyai/trustyai-service-operator-ci:6cbe93c6711d40e8b6f531e670885c45988d28b8

📦 LMES driver image: quay.io/trustyai/ta-lmes-driver:6cbe93c6711d40e8b6f531e670885c45988d28b8

📦 LMES job image: quay.io/trustyai/ta-lmes-job:6cbe93c6711d40e8b6f531e670885c45988d28b8

🗂️ CI manifests

[yhwang]

/LGTM

one thought is: should the value be configurable or auto-detect based on the namespace's info of the job. Or if it could be removed. We can create a discussion issue for that.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: RobGeada, yhwang

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

Needs approval from an approver in each of these files:

• OWNERS

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

[ruivieira]

@yhwang I've removed the user id in #322 and in my testing it works fine. Letting OpenShift automatically assign the user id (based on SCC and the relevant namespace range) seems to be enough.

We can move any discussion to #322, but in the meantime I'm closing this PR.