_check_vdisk_fc_mappings does not handle snapshot mapping cleanup associated with volumes

[Chhavi Agarwal]

If the volume has multiple fcmapping for snapshot and clones the check_vdisk_fcmapping fails fcmap cleanup

seCases:
1. Create 1 source volume, using source volume create 2 snapshots and 2 clone volumes.
    a. Delete the source volume when clone is in progress(fc state is copying).
    b. Delete the source volume when clone is 100% completed and fcmap is auto deleted.
    c. Delete the source volume when clone is 100% completed and fcmap is not deleted.(state is copying and progress is 100%)
    d. Delete the source volume when clone volumes fcmap state is in prepared,idle_or_copied.
    e. Repeat a,b,c,d for deleting the clone volume
2. create 1 source volume, using source volume create 2 snapshots.
    a. Delete the source volume for snapshots when fcmap state is in copying.
    b. Delete the source volume for snapshots when fcmap state is in idle_or_copied.
    c. Delete the source volume for snapshots when fcmap state is in prepared.
    d. Repeat a,b,c for deleting the snapshot volume.
3. Create 1 source volume, using source volume create 2 snapshots and using snapshots create 2 clone volumes.
    a. Delete the snap volume when clone is in progress(fc state is copying).
    b. Delete the snap volume when clone is 100% completed and fcmap is auto deleted.
    c. Delete the snap volume when clone is 100% completed and fcmap is not deleted.(state is copying and progress is 100%)
    d. Delete the snap volume when clone volumes fcmap state is in prepared,idle_or_copied.
    e. Repeat a,b,c,d for deleting the clone volume and source volume.

[Girish_IBM (girishibm)]

Review link for check_vdisk_fc_maping clean up.
link: https://review.opendev.org/#/c/744664/

[Girish_IBM (girishibm)]

created defect for clean up of fcmaps in check_vdisk_fcmappings, below is the defect details.
https://bugs.launchpad.net/cinder/+bug/1890254