Name the production Vault after the exch product

The internal name of the product is exch, like its production server.
Paths, the Compose project, the Docker network, raft node ids and the
transit seal key and policy use it before the first rollout, so nothing
has to be renamed once data exists.

infra/prod/vault/config/vault-2.hcl

@@ -1,4 +1,4 @@
-# SXCHNGE production Vault, node 2. Only api_addr, cluster_addr and node_id
+# Production Vault, node 2. Only api_addr, cluster_addr and node_id
 # differ between the three node files.
 ui            = true
 disable_mlock = true
@@ -15,7 +15,7 @@ listener "tcp" {
 
 storage "raft" {
   path    = "/vault/file"
-  node_id = "sxchnge-vault-2"
+  node_id = "exch-vault-2"
   retry_join { leader_api_addr = "http://192.168.10.191:8200" }
   retry_join { leader_api_addr = "http://192.168.10.191:8210" }
   retry_join { leader_api_addr = "http://192.168.10.98:8200" }
@@ -26,5 +26,5 @@ storage "raft" {
 seal "transit" {
   address    = "https://vault.sendico.io"
   mount_path = "transit/"
-  key_name   = "sxchnge-vault-unseal"
+  key_name   = "exch-vault-unseal"
 }