Detect Sync/Async DRPolicy based on peerClasses status output and not spec.Region values in DRCluster

[ShyamsundarR]

Currently when a DRCluster resource is created, it expects a spec.Region value. This value when it is the same across DRClusters in a DRPolicy indicates that the clusters are in a Sync DR relationship, and when different, indicates Async DR relationship.

Instead of the user having to provide these values, we can leverage the DRPolicy peerClasses status output to determine if a pair of clusters are in a Sync or Async relationship based on the storageID values of the StorageClasses in these clusters.

This removes one hurdle when configuring a DRPolicy and its DRClusters.