Update metadata.name to match the destination service
I felt like using the destination service as the metadata.name value was more inline with how the service intentions work, plus made it more intuitive to add the public-api as a source of payments traffic.
I felt like using the destination service as the metadata.name value was more inline with how the service intentions work, plus made it more intuitive to add the
public-apias a source ofpaymentstraffic.