Run tunnel with Go SDK

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Network project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe your problem

I got started with the Ory network and looked into new ways of solving authentication (and authorization) for my projects. Ory looked promising, but in the end we decided against using Ory because running the tunnel with a separate CLI on every dev environment as well as on integration environments seemed like a bad developer experience due to the additional requirements.

Describe your ideal solution

Instead of requiring a separate CLI to be installed that then runs the tunnel, this should be part of the Go SDK, so that you just have a single Go application where you can optionally run the tunnel as well.

Workarounds or alternatives

• Adding the CLI as part of our Docker image
• Add taskfiles to streamline the experience for other devs who need to install and run the ORY tunnel

Version

v1.1.41

Additional Context

No response

Start by locating the Go SDK entry points and the existing tunnel CLI referenced in the issue. Compare how the CLI is invoked in development and integration environments, then define the SDK surface needed for optional tunnel execution. Done means a Go application can run the tunnel without requiring a separately installed CLI.