Data Factory Integration Runtime with Managed VNet using Azure CLI

**Is your feature request related to a problem? Please describe.**
I am trying to create a data factory setup using Azure CLI for all required configurations.
I am facing a problem that I cannot create an Integration Runtime enabled with VNET using Azure CLI.
I am able to create the managed VNet using `az datafactory managed-virtual-network create`
I am able to create a managed integration runtime using `az datafactory integration-runtime managed create`
But there is no way to set the mananged VNet in this integration runtime by using Azure CLI.

**Describe the solution you'd like**
I would like to be able to create a Data Factory Integration Runtime enabled with VNET using Azure CLI.
I would suggest to add a parameter `--managed-virtual-network` on the `az datafactory integration-runtime managed create` command that will accept a json for the VNet (the same way as the `--compute-properties` parameter works in the same command)

**Describe alternatives you've considered**
Using Azure PowerShell seems to be the way to go, but I have done everything else with Azure CLI and I would like to be able to complete everything using Azure CLI.
https://docs.microsoft.com/en-us/azure/data-factory/managed-virtual-network-private-endpoint#create-managed-virtual-network-via-azure-powershell

**Additional context**
While at it, please review that `az datafactory managed-virtual-network create` requires a parameter for`name` of the managed VNet, but if this name is something different than `default` (actual value for the name), then the UI for Integration Runtimes shows error message that the "default" managed VNet does not exist. Also if someone makes the mistake to create a managed network with different name, there is no way to rename or delete it (with Azure CLI at least) and also a second managed vnet cannot be created. So the only way out of this problem that I found was to delete the Data Factory resource and recreate it and then create again a Managed VNet named "default". I suggest that the "name" parameter is removed from `az datafactory managed-virtual-network create` or at least make it optional and write in the docs about the requirement to use the value "default" as name.