Current FNM BGP implementation cannot have different local ASN per BGP peer.

In order to have one FNM installation for different ASNs (different PODs Routers, Border Leafs) and make it iBGP relationship from Router, Border Leaf perspective it's desired to have ability to configure different local_ASN per BGP peer. Local Go-bgp implementation should not follow default BGP Updates propagation rules (should not work as common BGP speaker)