[projects] Fix workspace/project association when based on a prebuild

[jankeromnes]

Bug description

Follow-up to #6071 and #6097

When starting a workspace without a prebuild, the Project association is now correct.

However, when starting a workspace based on a prebuild, it automatically gets associated to the same Project as the prebuild (which can be a now-deleted Project, a project you're not a member of, or an older Prebuild without a project):

gitpod/components/server/ee/src/workspace/workspace-factory.ts

Line 214 in 811a6af

projectId: context.prebuiltWorkspace.projectId,

Steps to reproduce

1. Open a workspace on a repository that has a prebuild associated to a Project you don't have access to (e.g. https://gitlab.com/AlexTugarev/testing5888 if you're not Alex), or an older prebuild that has no Project associated (e.g. https://github.com/gitpod-io/browser-extension)

Expected behavior

No response

Example repository

No response

Anything else?

No response

[jankeromnes]

/schedule

[roboquat]

@jankeromnes: Cannot schedule issue - issue does not belong to a team. Use /team to specify one.

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jankeromnes]

/team meta

[jankeromnes]

/schedule

[roboquat]

@jankeromnes: Issue scheduled in the meta team (WIP: 0)

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jankeromnes]

/assign @AlexTugarev

[jankeromnes]

/state in-review

[jankeromnes]

/status in-review