IPaddr2 considers a cloned ip on lo as a cluster ip

I'm running a simple symmetric cluster, resources are configured like this :

```
primitive ip-ldap-lo ocf:heartbeat:IPaddr2 \
params ip="10.0.1.7" cidr_netmask="32" nic="lo" \
op monitor interval="60"
primitive slapd ocf:heartbeat:slapd params....
group ip-slapd ip-ldap-lo slapd
clone c-ip-slapd ip-slapd meta interleave="true"
```

This is "backend cluster" for IPVS/DR
In that case IPAddr2 is assuming the ip as a cluster ip. I don't need it ! :)

Looking at the https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/IPaddr2 i can see:
- L76 OCF_RESKEY_unique_clone_address defaults to false
- L384 it sets IP_INC_GLOBAL to OCF_RESKEY_CRM_meta_clone_max
- L467 it decides there's a need for a cluster_ip

what do you reckon ?
Is this a correct use-case ?
If so, how would change the behavior ?
how about adding a && [ "$NIC" != "lo" ] line 467 ?

Read heartbeat/IPaddr2 around lines 76, 384, and 467, focusing on how cloned resources on the loopback interface are classified. Verify whether this IPVS/DR use case should avoid cluster-IP handling and determine the intended behavior for a cloned address on lo; done means the behavior is decided and covered by the relevant validation.

Written by the indexing model from the issue text.