fix: temporary patch for Fastly service lookup domain

[vigneshrajsb]

Summary

This PR applies a temporary compatibility patch for Fastly service lookup naming in Lifecycle.

Current lookup logic builds Fastly service names using:

• fastly.${domainDefaults.http}

In our environment, domainDefaults.http and the fasly urls are different

This mismatch causes lookup failures and prevents Fastly-dependent PR comment actions from rendering (for example the purge checkbox).

Change

In src/server/lib/fastly.ts, getFastlyUrl() now uses a temporary normalization:

• return `fastly.${domainDefaults.http.replace(/^lifecycle\./, '')}`;

Why temporary

This is intentionally a short-term fix to unblock lookup behavior.
Fastly integration should be reworked into a dedicated app/service and driven by explicit Fastly domain/config instead of deriving from domainDefaults.http.

Inline comments were added in code to make this temporary status explicit.

Risk / Impact

• Scope is limited to Fastly lookup/purge/dashboard URL resolution paths.
• No global domainDefaults.http behavior was changed.
• Existing behavior for non-lifecycle. domains remains unchanged.

Follow-up

• Move Fastly logic out of this app into dedicated integration service.
• Replace this normalization with explicit Fastly base domain config per environment.