Convert Kuttl test 1-098_validate_dex_clientsecret to Ginkgo test format

[Naveena-058]

What type of PR is this?
/kind code-refactoring

What does this PR do / why we need it:
Changes:

• Converts Kuttl test to Ginkgo format: 1-098_validate_dex_clientsecret_deprecated.go
• Maintains the same test functionality: validates dex client secret is properly copied from service account token to argocd-secret
• Uses proper Ginkgo/Gomega patterns and fixtures (argocdFixture, k8sFixture, fixtureUtils)
• Implements parallel test structure with proper namespace isolation and cleanup
• Follows existing codebase patterns and conventions

Have you updated the necessary documentation?

• Documentation update is required by this PR.
• Documentation has been updated.

Which issue(s) this PR fixes:
Part of Kuttl to Ginkgo migration effort

Fixes #?
https://issues.redhat.com/browse/GITOPS-7205

Test acceptance criteria:

• Unit Test
• E2E Test

How to test changes / Special notes to the reviewer:

[openshift-ci]

@Naveena-058: The label(s) kind/code-refactoring cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?
/kind code-refactoring

What does this PR do / why we need it:
Changes:

• Converts Kuttl test to Ginkgo format: 1-098_validate_dex_clientsecret_deprecated.go
• Maintains the same test functionality: validates dex client secret is properly copied from service account token to argocd-secret
• Uses proper Ginkgo/Gomega patterns and fixtures (argocdFixture, k8sFixture, fixtureUtils)
• Implements parallel test structure with proper namespace isolation and cleanup
• Follows existing codebase patterns and conventions

Have you updated the necessary documentation?

• Documentation update is required by this PR.
• Documentation has been updated.

Which issue(s) this PR fixes:
Part of Kuttl to Ginkgo migration effort

Fixes #?
https://issues.redhat.com/browse/GITOPS-7205

Test acceptance criteria:

• Unit Test
• E2E Test

How to test changes / Special notes to the reviewer:

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.

[openshift-ci]

Hi @Naveena-058. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[varshab1210]

/ok-to-test

[alkakumari016]

/retest

[svghadi]

/lgtm

[svghadi]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: svghadi

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 [svghadi]

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

[svghadi]

/lgtm