federation: some logs don't reference ServiceMeshPeer name

It can be hard to understand which ServiceMeshPeer is affected if we don't log their names. In this example, a watch has failed but there might be multiple if you have more than one SMP resource, so it's not immediately clear which ServiceMeshPeer is affected without looking at the resource's status.

2021-09-07T08:19:11.828046Z	info	federation	starting watch	component=federation-registry
2021-09-07T08:19:11.843098Z	error	federation	watch failed: status code is not OK: 403 (403 Forbidden)	component=federation-registry

Acceptance Criteria:

• all federation-related log outputs should reference the names of resources they're reconciling