Simplify the build/push access for quay.io repositories belonging to non-default organizations or users.

[tumido]

Is your feature request related to a problem? Please describe.
When setting up the build pipeline via .aicoe-ci.yaml sometimes you'd like to publish to other Quay.io organization than aicoe org. Currently the integration process for a "new" quay organization can be quite tedious. User has to have an robot account with write access, send the access token to the AiCoE-CI team so it is deployed as a secret resource in the CI namespace and then obtain the actual secret name that they can reference in their .aicoe-ci.yaml.

Describe the solution you'd like
Would it be possible to either:

• Add a AiCoE-CI user/robot account to the repository on quay with write access (then no build secret needs to be set up and CI can use some default token for this "AiCoE-CI" user).
• Read the token from repository secrets as other CI's usually do it - so the repository maintainer has control over what token is being used and who else has access to their repository.

Describe alternatives you've considered
n/a

Additional context
n/a

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[harshad16]

/remove-lifecycle stale

[MichaelClifford]

Just to add to this issue. We are trying to improve the docs for Elyra tutorial, and one of the instructions for setting up quay is:
Click on the Robot creation, goto kubernetes secret and pass on that information to aicoe-ci instance. Currently you would have to pass it on by contacting us, we are still trying to figure out some alternative

Until this issue is sorted and the process is made simpler. How should someone (outside of our org) "contact us" to provide their credentials? Is there an aicoe-ci email address that can be used? should they reach out to a specific person on slack?

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[goern]

/remove-lifecycle forzen
/remove-lifecycle stale

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[harshad16]

/remove-lifecycle stale
/lifecycle forzen

[harshad16]

/lifecycle frozen