Publish cloud function as `@mdn/dex-cloud-server`

What information was incorrect, unhelpful, or incomplete?

Fred needs to run the Dex cloud function as its local ingress server, but the cloud-function package is private and only runnable from a Dex checkout.

Requiring a sibling Dex checkout would make Fred's development setup difficult to install and version consistently.

What did you expect to see?

Publish cloud-function as the public npm package @mdn/dex-cloud-server.

The package should:

• Provide a dex-cloud-server executable that starts the existing mdnHandler.
• Continue supporting deployment through Google Cloud Functions.
• Expose the handler or createHandler through a package export where useful for testing.
• Include the runtime files required to start the server.
• Support CANONICALS_FILE and REDIRECTS_FILE.
• Be published with npm provenance through an automated release workflow.

Fred can then depend on a pinned package version and run Dex as a separate local process.

Do you have any supporting links, references, or citations?

Blocked by:

• https://github.com/mdn/dex/issues/526

Do you have anything more you want to share?

Integrating the package into Fred's development startup and providing combined Fred and Dex PR preview deployments are outside the scope of this issue. PR previews are worth investigating after Fred uses the published Dex server.

Start by checking the blocking issue #526, then inspect the existing cloud-function package and its mdnHandler/createHandler entry points. Trace the runtime files, executable setup, and deployment configuration before deciding where the automated npm release workflow belongs. Done means @mdn/dex-cloud-server can run the handler, remain deployable as a Google Cloud Function, support both file environment variables, and expose the useful handler export.