move tb-build-02 to gnt-chi cluster

the tb-builder regularly trigger load warnings in the main ganeti cluster (gnt-fsn, see #40100 (closed)). create a new tb-build-xx machine into the alternate cluster (gnt-chi) to free up resources in the main cluster. this also involves shutting down one of the existing tb-build machines, obviously.

in any case, I'd like to hear more from the TB team how they think we should handle this problem. what would be involved would be basically a hostname and IP address change, as we'd rebuild the box from scratch in a new cluster.

/cc @gk @boklm @sysrqb

comments? suggestions?

the cluster's disks may be slower: they are backed by an iSCSI SAN with SAS disks (as opposed to local, possibly more modern SATA disks), but there's plenty of RAM and decent processors. the hardware inventory is available for those of you who are curious.

the boxes were created by @hiro in #34122 (closed), and are hopefully all in puppet, profile::torbrowser_build.

update: move was approved, tb-build-03 was created, tb-build-02 retirement checklist:

1. announced the change (here, last week, and before)
2. remove host from nagios
3. stop VM
4. after delay, retire host from parent, backups, and puppet
5. remove from LDAP
6. power-grep to remove the IP
7. remove from tor-passwords
8. remove from DNSwl (N/A)
9. remove from wiki, inventory (N/A)
10. N/A
11. remove from reverse DNS