Update testnet.polykey.io to point to the list of IPs running seed keynodes

[CMCDragonkai]

Done on cloudflare.

This will depend on us deploying the js-polykey keynode containers onto AWS.

Also change bootstrap.polykey.io to seed.polykey.io.

[CMCDragonkai]

@joshuakarp we have agreed to use the term "seed" rather than "bootstrap" or "broker".

So this should now be called seed.polykey.io and all other uses should be seed.

[joshuakarp]

Uses of broker still needs to be refactored as seed throughout the nodes domain.

[joshuakarp]

Furthermore, I should remove the separation of brokerNodeConnections to just be normal nodeConnections. Seed nodes are just nodes that we provide to a new keynode to "introduce" the keynode to the larger Polykey network. They aren't special. See a previous message from me for context:

There's a couple of reasons why the brokers are separate:

• To establish a connection to them, it's assumed a direct connection is possible (so no need for hole-punching)
• I don't add their details into the buckets database at all. I believe my assumption was that they are probably going to be 'owned' by us as Matrix AI, and they shouldn't be discoverable by other nodes (from getClosestGlobalNodes)

I know you said before that the broker nodes could be any node in the network though, and thinking about this some more now, it would probably make sense for these nodes to just be integrated like any other node. Unless we are treating them as something special (like a central 'Polykey' keynode)

[CMCDragonkai]

So no both bootstrap nor seed.

The mainnet and testnet is more explanatory.

[joshuakarp]

This issue is also related to #269.