AKS vnet resource group

[scottboring]

Adding optional flag for vnet resource group for scenarios when the vnet is in a different resource group from the AKS resource

Description

The virtual network is not always in the same resource group as the AKS resource and subsequently this needs to be exposed as a param to the CLI

Fixes #(issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

• Executed CLI using param and verified param was used
• Executed CLI without param and verified param defaulted to resource-group-name

[adamjensenbot]

Hi @scottboring. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
  when the rebase operation is completed)
• /merge: Merge this PR into the master branch
• /build Build Liqo components
• /test Launch the E2E and Unit tests
• /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

• kind/breaking: 💥 Breaking Change
• kind/feature: 🚀 New Feature
• kind/bug: 🐛 Bug Fix
• kind/cleanup: 🧹 Code Refactoring
• kind/docs: 📝 Documentation

[cheina97]

/rebase test=true

[aleoli]

Hi @scottboring! Thanks for your contribution!

[aleoli]

/merge