When using clustering with replication, linkstate topology of non-leaders is not available via restconf

Using 3-node cluster, setup using instructions from here https://wiki.opendaylight.org/view/BGP_LS_PCEP:Lithium_User_Guide

Each node is BGP peering with a separate Cisco XRv instance. Even though each router is sending linkstate update to node, only the topology for shard leader shows up in http://localhost:8181/restconf/operational/network-topology:network-topology/ output

Each node is configured for different rib-id and topology-id as per the instructions. The topology-provider on each node listens on data changes in associated RIB’s sub-tree. Since both config and operational stores are replicated in default config, DataTreeChangeListener is invoked only on the leader node which is not listening on RIB’s used by other 2 nodes and so those changes get lost. If ClusteredDataTreeChangeListener is used instead, it will ensure that changes are seen on all nodes and are acted upon by each node for the RIB it is using
https://lists.opendaylight.org/pipermail/controller-dev/2015-November/010991.html

If BGP shards are not replicated, this problem may not happen, but since that is not the default config, opening this bug to evaluate using ClusteredDataTreeChangeListener in the code which will work irrespective of whether BGP shards are enabled