When the server calls its own API it should not need to route via the internet

[iainsproat]

What package are you referring to?

Speckle Server

Describe the bug

The server calls its own GraphQL API in a number of locations. See example. These currently use the canonical domain.

In cases where this is a non-localhost and non-IP value, the call will likely be routed via the internet. Ideally we should ensure that all calls are sent via local loopback, i.e. to localhost, or - where deployed on kubernetes it would also be acceptable to send to a kubernetes service url speckle-server.speckle-namespace.svc.cluster.local., as this would provide some load balancing.

To Reproduce

1. Enable Cilium Network Policy for speckle-server.
2. Modify the Cilium Network Policy to remove egress from speckle-server to the internet or to the canonical domain.
3. Attempt to import a file, triggering this call from speckle-server to the canonical url.

Expected behavior

Speckle-server should not require egress to the internet to call its own API.

Screenshots

System Info

Failure Logs

Additional context

#913

Proposed Solution (if any)

These calls should not use CANONICAL_URL environment variable and should instead use a separate environment variable; which is either a local loopback or a kubernetes service url.

[iainsproat]

Closed in lieu of https://linear.app/speckle/issue/WEB-1626/speckle-server-components-should-not-inter-connect-via-the-public