[v1.16] chore: update to argocd-operator '081f799da834ec9263fd0328ebb999974aef9259'

[jgwest]

What type of PR is this?
/kind bug

What does this PR do / why we need it:

Update to latest from release-0.14 of argocd-operator

[openshift-ci]

[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 assign varshab1210 for approval. For more information see the Code Review Process.

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

Details

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

[jgwest]

/retest

CI fail for 2, and generic kuttl flake for 1

[jgwest]

/retest
cluster init fail

[jgwest]

Parallel:

--- FAIL: kuttl/harness/1-005_validate_route_tls (1204.27s)\n       
--- FAIL: kuttl/harness/1-063_validate_statefulset_restart (1247.90s)

Sequential:

--- FAIL: kuttl/harness/1-035_validate_argocd_secret_repopulate (723.58s)

/retest

[openshift-ci]

@jgwest: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v4.17-kuttl-parallel	04bc42f	link	true	/test v4.17-kuttl-parallel

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[jgwest]

/retest

Parallel:

kuttl/harness/1-005_validate_route_tls 

https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/redhat-developer_gitops-operator/1025/pull-ci-redhat-developer-gitops-operator-v1.16-v4.17-kuttl-parallel/1996563999604346880

[jgwest]

The remaining test fail 1-005_validate_route_tls appears to be a bug fix that was backported to 1.16.x, but the kuttl test was not updated. So it's a test bug, not a product bug.

• The ApplicationSet webhook Route is using the constant appset-webhook, but the test is looking for example-applicationset-controller-webhook.
• It was intentionally shortened to reduce the number of characters in the Route name.

Given that, given that this release will be out of support shortly, and given that all other tests are passing, I am merging.