[content-init] Ensure .gitpod path is available

[csweichel]

Description

When repositories contain a .gitpod file this can cause the content initializer to fail because we use /workspace/.gitpod internally. This change introduces special handling such cases where we try to git mv or mv the .gitpod file to .gitpod.yaml. If .gitpod.yaml already exists, we delete .gitpod.

Related Issue(s)

Fixes #7694

How to test

Open https://cw-fix-7694.staging.gitpod-dev.com/#https://github.com/csweichel/gitpod-hello-ui-demo
If the build starts (might not complete due to other issues), we're good. Compare with prod where the build fails to start due to a content init error.

Release Notes

NONE

[csweichel]

/werft run

👍 started the job as gitpod-build-cw-fix-7694.8

[codecov]

Codecov Report

Merging #7749 (5aafeea) into main (9a7411f) will increase coverage by 18.47%.
The diff coverage is 2.56%.

@@             Coverage Diff             @@
##             main    #7749       +/-   ##
===========================================
+ Coverage   11.54%   30.02%   +18.47%     
===========================================
  Files          20      106       +86     
  Lines        1169    17435    +16266     
===========================================
+ Hits          135     5234     +5099     
- Misses       1031    11750    +10719     
- Partials        3      451      +448     

Flag	Coverage Δ
components-content-service-app	13.92% <2.85%> (?)
components-content-service-lib	13.92% <2.85%> (?)
components-gitpod-cli-app	10.38% <ø> (+0.09%)	⬆️
components-image-builder-mk3-app	35.26% <ø> (?)
components-local-app-app-darwin-amd64	?
components-local-app-app-darwin-arm64	?
components-local-app-app-linux-amd64	?
components-local-app-app-linux-arm64	?
components-local-app-app-windows-386	?
components-local-app-app-windows-amd64	?
components-local-app-app-windows-arm64	?
components-supervisor-app	35.43% <ø> (?)
components-ws-daemon-app	22.04% <0.00%> (?)
components-ws-daemon-lib	22.04% <0.00%> (?)
components-ws-manager-app	40.77% <ø> (?)
components-ws-proxy-app	68.32% <ø> (?)
installer-raw-app	5.75% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...nts/content-service/pkg/initializer/initializer.go	4.66% <0.00%> (ø)
components/ws-daemon/pkg/content/initializer.go	0.00% <0.00%> (ø)
components/content-service/pkg/git/git.go	36.93% <33.33%> (ø)
components/local-app/pkg/auth/auth.go
components/local-app/pkg/auth/pkce.go
components/ws-manager/pkg/manager/manager_ee.go	0.00% <0.00%> (ø)
components/supervisor/pkg/supervisor/services.go	21.56% <0.00%> (ø)
components/ws-proxy/pkg/proxy/auth.go	100.00% <0.00%> (ø)
components/ws-manager/pkg/manager/imagespec.go	0.00% <0.00%> (ø)
components/ws-manager/pkg/clock/clock.go	68.62% <0.00%> (ø)
... and 84 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4a907f9...5aafeea. Read the comment docs.

[roboquat]

LGTM label has been added.

Git tree hash: 19fffa7b50f5ea26c32bd20de38c2f71cb6b870f

[roboquat]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Furisto

Associated issue: #7694

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• components/content-service/OWNERS [Furisto]
• components/ws-daemon/OWNERS [Furisto]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment