workaround for broken testnet hare3 protocol name (#6728)

Author: poszu

api/node/client/client.go

@@ -129,6 +129,12 @@ func (s *NodeService) Publish(ctx context.Context, proto string, blob []byte) er
 	// The `hare3.DefaultProtocolName` contains slashes which
 	// makes it unsuitable for a path parameter,
 	// thus we change it to hare3 here and backwards on the server side.
+	// FIXME: we check if `proto == ""` because the testnet config has
+	// empty hare3 proto in `config/presets/testnet.go`.
+	// Remove it after fixing the testnet preset.
+	if proto == "" {
+		proto = "testnet-hare3-workaround"
+	}
 	if proto == hare3.DefaultProtocolName {
 		proto = "hare3"
 	}

api/node/server/server.go

@@ -261,6 +261,13 @@ func (s *Server) PostPublishProtocol(
 	}
 
 	protocol := string(request.Protocol)
+	// FIXME: we check if `proto == "testnet-hare3-workaround"` as a workaround for
+	// an empty hare3 proto in `config/presets/testnet.go`.
+	// The client set "testnet-hare3-workaround" and we change back to "".
+	// Remove it after fixing the testnet preset.
+	if protocol == "testnet-hare3-workaround" {
+		protocol = ""
+	}
 	if protocol == "hare3" {
 		// Revert protocol change (avoiding slashes) done on the client side.
 		// TODO: hare3 takes that from configuration what also should be done