Ability to Self‑Host Newt Install Script & Client Downloads

[RobbyV2]

Summary

Add support for hosting the Newt installer script and client binaries directly on a self‑hosted Pangolin instance, removing the dependency on pangolin.net or GitHub Releases.

Motivation

In self‑hosted or restricted environments, relying on external infrastructure (pangolin.net or GitHub Releases) to download Newt (or now the newt sh installer script) and other new client binaries creates friction and sometimes makes deployment impossible.

Organizations with air‑gapped networks, strict compliance requirements, or internal‑only infrastructure need a way to distribute Newt entirely from their own Pangolin instance.

Supporting self‑hosted distribution would resolve this and potentially provide some more control.

Proposed Solution

Potentially something that:

• Hosts Newt and other platform specific client binaries/install scripts for the supported platforms
• Serve a self‑contained installer script (e.g., get-newt.sh) that points to the self‑hosted instance

And then we can automatically sync or even manually upload scripts or binaries.
To complement this maybe have an API with the current server software versions, a call to force synchronize, or reference to get the latest ones online (this may exist, I'm not sure)

Example endpoint structure:
https://pangolin.example.com/downloads/newt//

This would allow users to install Newt with a command like:
curl -fsSL https://pangolin.example.com/get-newt.sh | sh

Alternatives Considered

Something else is to do something like mirroring the repositories of different binaries and building internally/on-demand, but this is not really needed; could be interesting though

Additional Context

No response