NetApp SolidFire: Fix replication

This patch addresses several of the problems currently found in this
driver:

 - When creating a SolidFire volume with a volume type that has
replication enabled the replication_status of this volume was not
changing.
 - During initialization, if a cluster is already paired, the driver
fails to load.
 - Driver does not create volumes on the replication target on
several configurations. For example, if the volume is being
created from a snashot or from another volume, etc.
 - During Failback, the driver doesn't update iSCSI connection
info to the secondary cluster nor the volume's replication status.

Closes-bug: #1834013
Closes-bug: #1751932
Change-Id: I920f958db1d48e52b548082d852c03f427a279ca
Co-Authored-By: Fernando Ferraz <sfernand@netapp.com>
Co-Authored-By: Thiago Correa <thiago.correa@netapp.com>
(cherry picked from commit 215d6b2b27)

releasenotes/notes/fix-solidfire-replication-dcb3e59b29950933.yaml

@@ -0,0 +1,8 @@
+---
+fixes:
+  - |
+    The SolidFire replication was fixed. Several bugs were addressed (creating
+    replicated volumes from snapshots, from volumes, retype a volume to a
+    replicated type, managing a volume to a replicated type, correctly
+    updating portal info on failover/failback and some minor
+    other fixes). Closes bugs #1834013, #1751932.