Description of Problem

• App creation panel pops up again upon closing it (intermittently) or on successful creation of the application
• `path` field is shown as a mandatory field only when clicked on `Create`

Additional Info

• This was tested on OCP 4.17 with GitOps 1.14.1 RC, needs to be checked on other versions

Problem Reproduction

• Head over to ArgoCD server UI (GitOps RC 1.14.1)
• Click on +NEW APP, close it, you might see it popping up again. 
• Create an application, you'll see that the screen pops up again even after the application has been created successfully

Reproducibility

• Intermittent

Prerequisites/Environment

• This was tested on OCP 4.17 with GitOps 1.14.1 RC, needs to be checked on other versions

Steps to Reproduce

• Same as `Problem Reproduction`

Expected Results

• App creation page disappears upon closing it or upon successful creation of the application

Actual Results

• App creation screen re opens

Problem Analysis

• <Completed by engineering team as part of the triage/refinement process>

Root Cause

• <What is the root cause of the problem? Or, why is it not a bug?>

Workaround (If Possible)

• <Are there any workarounds we can provide to the customers?>

Fix Approaches

• <If we decide to fix this bug, how will we do it?>

Acceptance Criteria

• Expected result is met

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.