Re-enable volume service test

[jochenehret]

What is this change about?

Fix the volume service acceptance test so that it works with the cf-deployment NFS service.

Please provide contextual information.

We want to validate the NFS service feature that is offered by cf-deployment:
https://github.com/cloudfoundry/cf-deployment/blob/main/operations/enable-nfs-volume-service.yml
The cf-deployment "fresh" environment will deploy the NFS broker and a test server:
cloudfoundry/cf-deployment#1204
Then we can activate the volume_service test on that environment:
https://github.com/cloudfoundry/relint-envs/pull/46

What version of cf-deployment have you run this cf-acceptance-test change against?

v43.3.0

Please check all that apply for this PR:

• introduces a new test --- Are you sure everyone should be running this test? -> test must be explicitly enabled
• changes an existing test
• requires an update to a CATs integration-config

Did you update the README as appropriate for this change?

• YES
• N/A

If you are introducing a new acceptance test, what is your rationale for including it CATs rather than your own acceptance test suite?

It's not strictly a new test, we want to re-enable an existing test.

How many more (or fewer) seconds of runtime will this change introduce to CATs?

150 seconds

What is the level of urgency for publishing this change?

• Urgent - unblocks current or future work
• Slightly Less than Urgent

[jochenehret]

CATs config json would need these parameters:

  "volume_service_name": "nfs",
  "volume_service_plan_name": "Existing",
  "volume_service_create_config": "{\"share\": \"nfstestserver.service.cf.internal/export/users\"}"

[winkingturtle-vmw]

We've now pulled in these changes, and verified that above changes will succeed for SMB broker as well.