Test attached volume extend actions in the nova-next job

Currently we don't have test coverage for volume extend of attached
volumes and we recently had a bug around extending attached LUKSv2
encrypted volumes.

This adjusts the test regex to include volume extend tests and enables
the corresponding features in the volume service so the tests will run.

Depends-On: https://review.opendev.org/c/openstack/tempest/+/836065

Related-Bug: #1967157

Change-Id: I13cd01fe15c935a235ec1abb7cfb62de1f15065f

.zuul.yaml

@@ -326,13 +326,15 @@
     post-run: playbooks/nova-next/post.yaml
     required-projects:
         - novnc/novnc
+        - openstack/os-brick
     vars:
       # We use the "all" environment for tempest_test_regex and
       # tempest_exclude_regex.
       tox_envlist: all
-      # Run all compute API tests and most scenario tests at the default
-      # concurrency (nproc/2 which is normally 4 in the gate).
-      tempest_test_regex: ^tempest\.(scenario|api\.compute)
+      # Run all compute API tests, most scenario tests, and extend attached
+      # volumes tests at the default concurrency (nproc/2 which is normally 4
+      # in the gate).
+      tempest_test_regex: ^tempest\.(scenario|api\.compute|api\.volume\.(admin\.)?test_(encrypted_)?volumes_extend\.(Encrypted)?VolumesExtendAttachedTest)
       # The tempest.scenario.test_network* tests are skipped because they
       # (1) take a long time and (2) are already covered in the
       # tempest-slow* job. If this regex gets more complicated use
@@ -388,6 +390,9 @@
               unified_limits: True
             neutron_plugin_options:
               available_type_drivers: flat,geneve,vlan,gre,local,vxlan
+            volume-feature-enabled:
+              extend_attached_volume: True
+              extend_attached_encrypted_volume: True
       devstack_localrc:
         Q_AGENT: openvswitch
         Q_ML2_TENANT_NETWORK_TYPE: vxlan