additionalRepositories path resolution when workspaceLocation is modified

In Gitpod configuration, the workspaceLocation property allows users to define a custom base directory for the main repository, moving away from the default /workspace root. To support multi-repo environments, the additionalRepositories key enables the cloning of secondary repositories into the same workspace.

A potential configuration boundary exists when both features are used simultaneously. While the main repository adheres to the defined workspaceLocation, it is unclear how relative paths specified in the checkoutLocation of an additionalRepositories entry are resolved.

Specifically, there is uncertainty whether a relative path for a secondary repository resolves against the custom workspaceLocation or remains anchored to the system default /workspace root. This behavior impacts the reliability of initialization scripts that assume a uniform directory structure for all cloned repositories.

• Does a relative checkoutLocation in additionalRepositories resolve relative to the top-level workspaceLocation?
• If workspaceLocation is omitted, does the resolution behavior for secondary repositories change?