fix: 🐛 sync using origin remote by default

[jbonadiman]

I believe this change should fix the errors related to tokens being expired or overall changes to the config not being used after the first clone.
Instead of relying explicitly or implicitly in the origin remote, I used the URL that we already combine every time as a parameter to the <repository> argument of the fetch and pull commands.
I tested this with a simple testcase that I created on purpose, if someone could please test this further (preferably with a real issue - the ones regarding the error code 128), that would be awesome.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 70dd245

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[AkashRajpurohit]

@jbonadiman can you list down the tests that you did as well?

[jbonadiman]

@jbonadiman can you list down the tests that you did as well?

I did the token expired test:

• using the Forgejo client, I cloned a private repository with a token, then I regenerated it and this caused the git client error code 128.
• using the GitHub client, I followed the same steps and also got the git client error code 128.

Applying the changes in this PR, made it work again.

[AkashRajpurohit]

LGTM!

[AkashRajpurohit]

This should address and close #53