Description of problem:

Gosmee flag does not work as expected in Pipelines as Code on OpenShift

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

User ran the following command:
tkn-pac bootstrap --force-gosmee
 
During the process, it still detected an OpenShift route and prompted:
👀 I have detected an OpenShift Route on: https://pipelines-as-code-controller-openshift-pipelines.apps.bruhl.ocp.vslen
? Do you want me to use it? No

Actual results:

Despite passing the --force-gosmee flag, the CLI still attempts to detect and prompt for an OpenShift route.

Expected results:

Using the --force-gosmee flag should skip OpenShift route detection and force the use of a gosmee proxy for GitHub webhook forwarding.

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

Environment:

• OpenShift: Running in a private network
• Client Tools:
  • tkn version: 0.40.0
  • tkn-pac version: 0.33.0
  • oc version: 4.17.16
  • Server Version: 4.18.9
  • Pipelines version: 0.68.0
  • Triggers version: 0.31.0
  • Chains version: v0.24.0
  • Operator version: v0.75.0

Additional info (Such as Logs, Screenshots, etc):

User is working in a restricted/private network where direct webhook access from GitHub is not possible. They want to use gosmee as the tunneling service to relay webhooks from GitHub.

Github issue: https://github.com/openshift-pipelines/pipelines-as-code/issues/2067