harness pull only support the git clone;

Description:

harness pull repo <repo_id> , works for the git clone, but later if some one wants to update the repo through git pull, it requires manual authentication step again, we should support id-less harness pull repo or may be clone and pull separately so that we can support the git pull and also may be git push because otherwise it doesn't add any advantage for the user he has to again enter the pat-token for the git pull.

We can otherwise also support validating the git directly and then onwards user can use git, we can like setup things for the repo.

Start by tracing the harness pull repo <repo_id> command and its git clone and authentication flow. Define whether id-less pull, separate clone and pull commands, or persistent git authentication is the intended behavior, then verify that subsequent git pull and possibly git push do not require manual PAT entry again.