fix extention update when not on main branch

[w-e-w]

Description

issue

I consider this issue to be quite severe, even though it doesn't currently impact normal users only advanced users and developers

currently if a user is using a branch of extension that is not the main branch
there will be an issue when they try to update the extension

in the check_updates code()
it checks for origin = repo.rev_parse('origin') whitch is the commit hash of the main branch and not the hash of the branch where the user is on

and later on when confirming the update fetch_and_reset_hard() will reset the extention repo to the commit of the main branch and Not the branch the usere is on

for normal users who never switches branches this is fine they should never encounter this issue

but for advanced users who knows how to use git that are deliberately on a different branch this would cause their extension to be hard reste the the master branch

or in development phase, where devs are working on a separate branch the could have there code accidentally hard reset (data loss) to

in the future is possible some extensions might decide to maintain different version compatibility in different branches

if user is using a branch of extension that is not the main branch
the user will be reseted to the main branch

this will also prevent extensions from maintaining compatibility for different versions on different branches
as it will be reset the the main branch

fix solution

repo.rev_parse(f'{repo.remote().name}/{self.branch}') when checking for update
and repo.git.reset(f'{repo.remote().name}/{self.branch}', hard=True) when applying the update

---

I have done my test and seems to work correctly
but if someone should probably verify again that I haven't screwed up

Checklist:

• I have read contributing wiki page
• I have performed a self-review of my own code
• My code follows the style guidelines
• My code passes tests