Support new annotation behavior on storage network

[albinsun]

Which issue(s) this PR fixes

Issue #1566

Why we need it

1. Compare to longhorn-v1.6.2, longhorn-v1.7.1 behaves a bit different about the instance-manager's annotation when storage-network is disabled.
2. This behavior change breaks some test cases includes:
   • test_0_storage_network.py::test_storage_network
   • TestImageWithStorageNetwork::test_delete_image::teardown
   • TestVMWithStorageNetwork::test_enable_storage_network_with_api_stopped_vm::teardown
   • TestVMWithStorageNetwork::test_enable_storage_network_with_cli_stopped_vm::teardown
3. Longhorn mainly controls k8s.v1.cni.cncf.io/networks but not k8s.v1.cni.cncf.io/network-status. However we still need to check the latter for address.

What this PR does

1. Add checking on k8s.v1.cni.cncf.io/networks annotation for storage-network enable/disable status.
2. Keep existed checking on k8s.v1.cni.cncf.io/network-status but only for address and name validation when enabling storage-network.
3. This fix is compatible with longhorn-v1.6.2 (harvester-v1.3.2).

Special notes for your reviewer

Validation

• harvester-install-and-test/72

  3 fails are due to single node cluster does not support VM migration.

  

• local ipxe-example
  

Additional documentation or context

n/a

[lanfon72]

@albinsun please test this on v1.2 and v1.3 accordingly.

[albinsun]

@albinsun please test this on v1.2 and v1.3 accordingly.

• v1.3.2 (harvester-install-and-test/73)
  

• v1.2.2 (harvester-install-and-test/74)
  

[lanfon72]

LGTM