lntest: avoid global ServeMux

Using the default, global ServeMux prevents the same process from
calling `lntest.NewNetworkHarness` multiple times, because we get a
panic when registering HTTP routes.

Instead, we use the ServeMux beloning to the fee service struct.

docs/release-notes/release-notes-0.13.1.md

@@ -42,6 +42,10 @@ tag](https://github.com/lightningnetwork/lnd/pull/5335). A new flag
 test](https://github.com/lightningnetwork/lnd/pull/5348) that would cause the
 test to assert the wrong balance (the miner fee wasn't accounted for).
 
+A bug has been [fixed](https://github.com/lightningnetwork/lnd/pull/5674) in 
+the `lntest` package that prevented multiple test harnesses to be created from 
+the same process.
+
 ## Forwarding Optimizations
 
 [Decoding onion blobs is now done in

lntest/fee_service.go

@@ -46,12 +46,14 @@ func startFeeService() *feeService {
 	f.Fees = map[uint32]uint32{feeServiceTarget: 50000}
 
 	listenAddr := fmt.Sprintf(":%v", port)
+	mux := http.NewServeMux()
+	mux.HandleFunc("/fee-estimates.json", f.handleRequest)
+
 	f.srv = &http.Server{
 		Addr:    listenAddr,
+		Handler: mux,
 	}
 
-	http.HandleFunc("/fee-estimates.json", f.handleRequest)
-
 	f.wg.Add(1)
 	go func() {
 		defer f.wg.Done()