Hitachi: Lost compatibility of GAD volume

[Atsushi Kawai]

Hitachi had released out-of-tree driver until OSP16.1 .
the drivers imply the features Global-Active Device("GAD") and Remote Replication.

When creating a pair of volume on GAD, volume data is copied from primary volume to secondary volume, and the pair is duplicated. Copy group is a group made up of copy pairs. Users can operate the pair in units of copy groups or pairs.

The out-of-tree driver creates copy group whose name includes unique identifier, to identify what copy groups are under control.
The identifier for GAD volume pair is "G" and it for Remote Replication volume pair is "U".

On the other hand, upstream driver since Antelope create a copy group whose name contains the identifier "U", even for GAD volume.

So, after upgrading the environment has upstream driver since Antelope,
operations for copy groups which are created by the out-of-tree driver have to be failed.

[Atsushi Kawai (atsushi-kawai-bu)]

Overview of GAD:
https://knowledge.hitachivantara.com/Documents/Storage/VSP_Gx00_and_VSP_Fx00/83-05-xx/Product_Overview/Software_components_and_features_of_VSP_Gx00_and_VSP_Fx00#High_availability_with_global-active_device
Overview of Remote replication:
https://knowledge.hitachivantara.com/Documents/Storage/VSP_Gx00_and_VSP_Fx00/83-05-xx/Product_Overview/Software_components_and_features_of_VSP_Gx00_and_VSP_Fx00#Hitachi_Remote_Replication_software

patch and blueprint to be added GAD feature for Hitachi driver:
https://review.opendev.org/c/openstack/cinder/+/796170
https://blueprints.launchpad.net/cinder/+spec/hitachi-gad-support

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/cinder/+/901318