NFS3 and iSCSI automation tests; Fix for NFS Cancel Maintenance

[sandeeplocharla]

Description

This PR has the following:

1. Automation tests for NFS3 and iSCSI protocols

   • To run the automation tests follow the below:

     • Run all 10 suites

       bash test/integration/plugins/ontap/run_tests.sh
       

       Run a single suite by tag

       bash test/integration/plugins/ontap/run_tests.sh <tag>
       | Tag | Suite |
       |-----|-------|
       | `nfs3_workflow` | NFS3 pool lifecycle |
       | `nfs3_with_volumes` | NFS3 pool with volumes |
       | `zone_pool` | NFS3 zone-scoped pool |
       | `nfs3_volume` | NFS3 volume lifecycle |
       | `vm_volume_workflow` | NFS3 VM volume attach/detach |
       | `iscsi_workflow` | iSCSI pool lifecycle |
       | `iscsi_with_volumes` | iSCSI pool with volumes |
       | `iscsi_zone_pool` | iSCSI zone-scoped pool |
       | `iscsi_volume` | iSCSI volume lifecycle |
       | `iscsi_vm_workflow` | iSCSI VM volume attach/detach |
       

2. Fix for Cancel maintenance not functioning properly in case of NFS3

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?