feat(sshtunnel): add provider

[zeyadmoslem]

This PR introduces a new SSH Tunnel provider command to manage multiple SSH tunnels via configuration. Key features include:

• Tunnel Management: Start and stop SSH tunnels based on a declarative YAML configuration.

• Authentication Support:

  • Password-based authentication (including 1Password integration)
  • SSH key authentication (including 1Password integration)

• 1Password Integration: Resolve passwords or private keys directly from 1Password vaults.

• Optional Sudo: Ability to run tunnels with sudo when required.

• Port Conflict Handling: Checks if the local port is already in use before starting a tunnel.

• Temporary Key Handling: Creates temporary files for private keys obtained from 1Password and cleans them up after use.

• CLI Integration: Fully integrated into the CLI with autocompletion and command tree support.

This provider enables secure and automated management of SSH tunnels for multiple environments, supporting both developer and CI/CD workflows.

For more information, please read the README.md.

[franklinkim]

Hi @zeyadmoslem, thanks for the PR. Did you check the implementation of kubeforward in combination with gokazi. It might be a simple way to check if the tunnel process is already running and also being able to add the checker

[zeyadmoslem]

Hi @franklinkim , thanks for the suggestion. Actually, at the beginning I tried to implement gokazi, but the issue is that I would have to provide the exact same command and arguments in gokazi.Add() that are built and run in the execute function’s start case; otherwise, it wouldn’t be recognized as running (the findProcess function in gokazi compares the arguments and fails if they don’t match). In some cases, building these arguments requires retrieving credentials from 1PW. This means that every time the shell starts or is rebuilt, the prompt would ask for authentication in 1PW before building or starting, if it’s not already authenticated.

Would you recommend implementing it this way for now, so that the prompt asks for 1PW authentication before starting, or should we leave it as is for now and refactor it later?