Implement a federation test

[murgatroid99]

This uses some of the tools that were originally implemented for the fallback test to implement a test for the federation feature. The test spreads resources across two control plane servers, so that both a client and a server need to use the authority information in the resource URLs to know which control plane server to request each resource from, and they need to contact both control plane servers to get their complete configurations. go-control-plane imposes some constraints on what combinations of resources it will serve, so both control plane servers have all of the server resources, but the specified authorities should cause the server to contact both anyway, and we attempt to confirm that by testing that it has a connection to both control plane servers.

While implementing this, I had to make a couple of changes that impacted the fallback test:

• I modified the bootstrap file template to include the federation fields, and I made the bootstrap generator function more general.
• I modified the resource generation code to be able to generate individual resources and group them together separately.

Test runs:

• grpc/java/master/branch/psm-light (the fallback test failed, but it is also failing the same way without this change)
• grpc/go/master/branch/psm-light
• grpc/core/master/linux/psm-light
• grpc/core/master/linux/psm-light-python
• grpc/node/master/psm-light

[murgatroid99]

Test runs after changes:

• grpc/java/master/branch/psm-light
• grpc/go/master/branch/psm-light
• grpc/core/master/linux/psm-light
• grpc/core/master/linux/psm-light-python
• grpc/node/master/psm-light

[murgatroid99]

• grpc/java/master/branch/psm-light
• grpc/go/master/branch/psm-light
• grpc/core/master/linux/psm-light
• grpc/core/master/linux/psm-light-python
• grpc/node/master/psm-light