Docs: replace dev-only URLs with relative links

[HussainAther]

What?

Replaces development-only URLs (e.g. localhost:3000, hubs.local:3000) in documentation with relative links.

Why?

Several docs pages referenced dev-only hosts, which break for readers on the published site and are confusing outside a local dev environment. Using relative links keeps navigation working in all environments (local, CI, and production).

Examples

N/A (documentation link cleanup)

How to test

1. Open the affected docs pages:
   • setup-custom-client
   • hubs-cloud-enable-scene-editor
   • hubs-cloud-importing-content
   • setup-updating
2. Click the updated links
3. Confirm they resolve correctly and no longer point to localhost or hubs.local

Documentation of functionality

The documentation changes are contained directly in this pull request.

Limitations

This PR only updates known dev-only URLs; it does not attempt a full audit of all external links.

Alternatives considered

Leaving the links unchanged was considered, but would continue to cause broken navigation for readers of the published docs.

Open questions

None.

Additional details or related context

This change is intentionally minimal and avoids altering URLs or page structure beyond fixing link targets.

[HussainAther]

This cleans up a handful of dev-only URLs (, ) that were leaking into published docs. Happy to extend this to a broader audit if useful.

[HussainAther]

This cleans up a handful of dev-only URLs (localhost, hubs.local) that were leaking into published docs. Happy to extend this to a broader audit if useful.

[HussainAther]

This cleans up a handful of dev-only URLs (localhost, hubs.local) that were leaking into published docs. Happy to extend this to a broader audit if useful.

[HussainAther]

This cleans up a handful of dev-only URLs (localhost, hubs.local) that were leaking into published docs. Happy to extend this to a broader audit if useful.

[Exairnous]

Thank you for the pull request. You haven't based this off of the latest changes from the master branch, so you would need to rebase on master before this can move forward. Most of what you have changed here has already been addressed by PR #214, except for the changes to docs/setup-updating.md.

[Exairnous]

Closing in favour of #252