Flexible and expressive traffic orchestration: introducing internal endpoints

The new internal endpoints and forward-internal action in ngrok enable flexible traffic orchestration, allowing developers to create arbitrarily flexible routing topologies so they can send their ngrok traffic where it needs to go. Internal endpoints are secure, non-public endpoints that end with the .internal TLD suffix, and can be created from the ngrok agent's CLI or through the dashboard. The forward-internal action forwards traffic from one endpoint to another or to a group of endpoints, providing a flexible way to manage traffic flow securely. With internal endpoints, developers can route traffic based on various aspects of an HTTP request, TCP connection, TLS handshake, or any of over 100 different variables available to their Traffic Policy rules. The new features enable use cases such as path-based routing, domain-based routing, header-based routing, geolocation-based routing by client location, and more. They are designed to be reusable and composable building blocks that can be used for various purposes beyond traffic orchestration, including self-service app delivery, centralized security, on-demand public addressability of endpoints, and debugging live traffic.