Why does the `SAPHana` resource agent erroneously report the System Replication state as SFAIL for the Slave/SECONDARY?

Issue

• This issue happens only in a Multitarget HANA System Replication environment, where there is a 3rd (DR) site which is not managed by Pacemaker and in combination with a version of the SAPHana and SAPHanaTopology resource agents lower than 0.162.1.
• When the 3rd (DR) site of a Multitarget HANA System Replication is unavailable for some unexpected reason (i.e. network disruption, crash of the system...), the SAPHana cluster resource marks the Slave/SECONDARY as SFAIL and it excludes this node as a possible takeover node, even if the replication from Master/PRIMARY to Slave/SECONDARY worked normally.