[Bug]: A project whose origin URL contains a space gets no repository identity #35034

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

On Linux, with a T3 Code server built from main and an empty database:

1. Make two Git repositories whose origin URLs differ only by a space: app with origin set to ssh://git@git.example.test/team repos/app.git, and control with origin set to ssh://git@git.example.test/team-repos/control.git.
2. Add both folders as projects on the server.
3. Read GET /api/orchestration/shell with a session token and look at each project's repositoryIdentity.

Expected behavior

Both projects get a repository identity from their origin URL. app reports ssh://git@git.example.test/team repos/app.git, the same way control reports its URL.

Actual behavior

app has no repository identity (null). control, whose URL has a dash where app has a space, resolves normally. git remote -v lists the spaced URL for app as usual.

Impact

Minor bug or occasional failure

Version or commit

main, commit b68aedf

Environment

Linux, T3 Code server from source on Node 26.12.1, empty database, no provider involved.

Logs or stack traces

$ git -C app remote -v
origin	ssh://git@git.example.test/team repos/app.git (fetch)
origin	ssh://git@git.example.test/team repos/app.git (push)
$ git -C control remote -v
origin	ssh://git@git.example.test/team-repos/control.git (fetch)
origin	ssh://git@git.example.test/team-repos/control.git (push)
$ GET /api/orchestration/shell | jq -c '.projects[] | {title, identity: .repositoryIdentity.locator.remoteUrl}'
{"title":"app","identity":null}
{"title":"control","identity":"ssh://git@git.example.test/team-repos/control.git"}

Screenshots, recordings, or supporting files

Workaround

None that I found.

A fix is in #28769.