chore: Smoke test for CLI - issue4393

[dewan-ahmed]

Checklist:

• (a) I've created an enhancement proposal and discussed it with the community.
• The title of the PR states what changed and the related issues number (used for the release note).
• I've updated documentation as required by this PR. --> Will be done once the entire Automated smoke test that mimics user behavior UI and CLI #4393 is completed.
• Optional. My organization is added to USERS.md.
• I've signed the CLA and my build is green (troubleshooting builds).

Background:

0. original issue
1. Cannot use existing helper functions e.g. fixture or RunCli and need to write new helper functions for smoke test. discussion
2. Expect that the session will already be authenticated by argocd login .... or caller of the function will provide a token to the test script.
3. The test should be able to run N times which is provided by the caller. discussion
4. The tests should run within "smoke-test" project. discussion

What's done with this PR:

1. Creating directory structure and pkg for the smoke test.
2. Creating RunCmd helper function
3. Adding test for argocd app create

What is to be done in future:

1. Adding CleanUp() function to delete existing app from namespace and existing tests from the project.
2. Adding argocd app sync and argocd app wait tests.
3. Adding error handling and fallback scenarios.

Assumption:

A caller of any of these smoke tests can run them for N times using Go's built-in capabilities:

go test -run <testname> -count N

Will this suffice?

[dewan-ahmed]

@amitkrout Adding the initial files per our discussion. Please review.

[jessesuen]

Is this ready for review? It appears to be failing linting/other tests. If not please mark as draft

[dewan-ahmed]

This PR is obsolete. Closing.