ROX-25847: add argocd types

[ludydoo]

Description

• Adding ArgoCD types for use with ctrlClient
• Not pulling the ArgoCD repository, because of potential dependency conflicts with Stackrox import
• Just copy-pasting the types from the ArgoCD repository

Checklist (Definition of Done)

• Unit and integration tests added
• Added test description under Test manual
• Documentation added if necessary (i.e. changes to dev setup, test execution, ...)
• CI and all relevant tests are passing
• Add the ticket number to the PR title if available, i.e. ROX-12345: ...
• Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.
• Add secret to app-interface Vault or Secrets Manager if necessary
• RDS changes were e2e tested manually
• Check AWS limits are reasonable for changes provisioning new resources
• (If applicable) Changes to the dp-terraform Helm values have been reflected in the addon on integration environment

Test manual

TODO: Add manual testing efforts

# To run tests locally run:
make db/teardown db/setup db/migrate
make ocm/setup
make verify lint binary test test/integration

[johannes94]

Did you try to add it as a Go dependency first and decided along the way that it wasn't worth the effort because of actual complexity in go.mod and conflicts with stackrox or is this a hypothesis that might never become true?

Asking because I'd honestly rather have a more complex go.mod as opposed to having to maintain this kind of implicit dependency over the lifetime of this product and possibly a lot of different ArgoCD versions in the long run.

[ludydoo]

I initially tried that, and got some errors. But I suspect a brain fart on my part. It's working well now by importing the repo directly, after updating the go.mod toolchain

[ludydoo]

/retest

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johannes94, ludydoo

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [johannes94,ludydoo]

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

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest

[ludydoo]

/retest