When opening an issue in Gitpod, the IDE now wants to push to the wrong upstream branch

[jankeromnes]

Bug description

Credit: @jbicker

Steps to reproduce

1. Open an issue in Gitpod
2. Make a commit
3. Click on "Push/Pull" in the status bar

⚠️ By default, the commit gets pushed to origin's default branch.

Expected behavior

Instead, the commit should be pushed to a new origin branch, with the same name as the local "issue" branch.

Example repository

No response

Anything else?

Likely a regression from #4167 which added a remote tracking branch to local issue-context branches:

gitpod/components/content-service/pkg/initializer/git.go

Lines 121 to 125 in 52a79bc

	} else if ws.TargetMode == LocalBranch {
	// checkout local branch based on remote HEAD
	if err := ws.Git(ctx, "checkout", "-B", ws.CloneTarget, "origin/HEAD"); err != nil {
	return err
	}

Judging from the git-checkout docs, it seems we could simply add --no-track to preserve the old semantics (i.e. no remote tracking branch for local issue-context branch).

[JanKoehnlein]

@jankeromnes can you fix that? This should likely be hotfix deployed. CC @csweichel