[BUG FIX] Remove ngrok version check everytime a op plugin command is called

[MOmarMiraj]

Overview

This MR will fix a bug regarding ngrok --version being called on every op plugin command.

Type of change

• Created a new plugin
• Improved an existing plugin
• Fixed a bug in an existing plugin
• Improved contributor utilities or experience

Related Issue(s)

• Resolves: #
• Relates: #

How To Test

The test pipelines should pass as usual and when running an op plugin command, if you check the activity monitor.. there should be no ngrok processes. (Note: Must have the ngrok CLI installed to test this)

Sometimes its hard to see the ngrok process on the activity monitor/task manager. An easier way to test is by changing L129 on plugins/ngrok/provisioner.go to open up any application you have on your PC and see if the app opens up when you run a op plugin command.

Changelog

The op plugin commands do not call a ngrok version check even if the ngrok plugin is not initialized.

[AndyTitu]

lgtm apart from the wording suggestion

[github-actions]

⚠️ This PR contains unsigned commits. To get your PR merged, please sign those commits (git rebase --exec 'git commit -S --amend --no-edit -n' @{upstream}) and force push them to this branch (git push --force-with-lease).

If you're new to commit signing, there are different ways to set it up:

Sign commits with gpg

Follow the steps below to set up commit signing with gpg:

1. Generate a GPG key
2. Add the GPG key to your GitHub account
3. Configure git to use your GPG key for commit signing

Sign commits with ssh-agent

Follow the steps below to set up commit signing with ssh-agent:

1. Generate an SSH key and add it to ssh-agent
2. Add the SSH key to your GitHub account
3. Configure git to use your SSH key for commit signing

Sign commits with 1Password

You can also sign commits using 1Password, which lets you sign commits with biometrics without the signing key leaving the local 1Password process.

Learn how to use 1Password to sign your commits.

[hculea]

Code looks good, and the changes make sense - calling the ngrok --version command only when actually provisioning and not in the Provisioner's instantiation.

Haven't functionally tested.