Remove source_replica info from api-ref

With the addition of schema validation and the release of cinderclient
4.0.0 we no longer accept source_replica as a volume creation parameter.
This was part of the short lived replication v1 functionality that was
removed several releases ago and never had support beyond one backend
type for one or two releases and has had no affect for quite a while
now.

Change-Id: Idd848628759884c1e637ca17dc292f776e4adf47
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

api-ref/source/v2/parameters.yaml

@@ -1498,13 +1498,6 @@ source_cgid:
   in: body
   required: false
   type: string
-source_replica:
-  description: |
-    The UUID of the replication volume to clone. This was for legacy
-    replication functionality and is no longer supported.
-  in: body
-  required: false
-  type: string
 source_volid:
   description: |
     The UUID of the source volume. The API creates a new volume with the same

api-ref/source/v2/volumes-v2-volumes.inc

@@ -191,7 +191,6 @@ Request
    - volume_type: volume_type_2
    - snapshot_id: snapshot_id
    - OS-SCH-HNT:scheduler_hints: OS-SCH-HNT:scheduler_hints
-   - source_replica: source_replica
    - metadata: metadata_2
    - project_id: project_id_path
 

api-ref/source/v3/parameters.yaml

@@ -2588,13 +2588,6 @@ source_reference:
   in: body
   required: true
   type: object
-source_replica:
-  description: |
-    The UUID of the replication volume to clone. This was for legacy
-    replication functionality and is no longer supported.
-  in: body
-  required: false
-  type: string
 source_volid:
   description: |
     The UUID of the source volume. The API creates a new volume with the same