Add Test: create volume with access:read-write and later change it to read-only

[shuklanirdesh82]

Requirement: at-least 2 docker VMs (VM1 & VM2) on the same ESX host

Test objective: update access option for the volume

1. covert read-only volume to read-write and back to read-only
2. covert read-write volume to read-only and back to read-write

Automation steps:

Steps for #1:covert read-only volume to read-write and back to read-only

create a volume Vol1 as ('access', 'read-only')
attach a container from VM1 and write to volume (make sure not able to wrire) and exit
access the volume from VM2 and try to write some data and make sure not able to write > exit
From ESX: set access permission as 'read-write'
try to write using any of the docker VM and make sure further write is possible as admin-cli has set the access as read-write
From ESX: set access permission back to 'read-only'
make sure from both nodes (VM1 & VM2); we are able to read and writes are not possible

Steps for #2:covert read-write volume to read-only and back to read-write

create a volume Vol1 as ('access', 'read-write')
attach a container from VM1 and write to volume and exit
access the volume from VM2 and read the data written by VM1 and modify the data to make sure VM2 is able to write to the volume and exit
From ESX: set access permission as 'read-only'
try to write using any of the docker VM and make sure further write is not possible as admin-cli has set the access as read-only
From ESX: set access permission back to 'read-write'
make sure further writes are available from both nodes i.e. VM1 & VM2

/CC @ashahi1 @kerneltime @pshahzeb

[kerneltime]

LGTM. We should also add a test to make sure we can convert a read-only drive to read-writable drive.

[tusharnt]

Manual execution of this test found #998.

Test automation is TBD.