Renewing access tokens fail when hosting gitlab in subpath
When self-hosting gitlab in a subpath the renewal of personal access tokens fails after update to 18.1.
For this example `<domain>` is the base domain and `<subpath>` is the sub path below the domain.
The browser console & access logs shows a `404` error for the following path:
`https://<domain>/<subpath>/<subpath>/-/user_settings/personal_access_tokens`
The `subpath` for gitlab appears twice in the url - this means users cannot renew their access tokens.