test: Fix failing exception check in new thread busy test

New thread busy test from 1238170
(bitcoin-core#214) is checking for
"Future already retrieved" error with string match which is fragile and does
not work on all platforms, resulting in error:

test/mp/test/test.cpp:339: error: failed: expected e.what() == std::string("Future already retrieved") [std::future_error: Future already retrieved == Future already retrieved]

This change fixes the test to check for an error code instead.

Separately there seems to be a problem with this KJ_EXPECT call because it
prints error output without causing the test to fail. This may be happening
because it is not called on the main test thread. That issue is not addressed
by this change and requires more followup.

Author: ryanofsky

test/mp/test/test.cpp

@@ -10,7 +10,6 @@
 #include <capnp/rpc.h>
 #include <condition_variable>
 #include <cstring>
-#include <exception>
 #include <functional>
 #include <future>
 #include <kj/async.h>
@@ -23,14 +22,15 @@
 #include <kj/test.h>
 #include <memory>
 #include <mp/proxy.h>
-#include "mp/proxy.capnp.h"
+#include <mp/proxy.capnp.h>
 #include <mp/proxy-io.h>
-#include "mp/util.h"
+#include <mp/util.h>
 #include <optional>
 #include <set>
 #include <stdexcept>
 #include <string>
 #include <string_view>
+#include <system_error>
 #include <thread>
 #include <utility>
 #include <vector>
@@ -333,9 +333,9 @@ KJ_TEST("Make simultaneous IPC callbacks with same request_thread and callback_t
         {
             signal.get_future().get();
         }
-        catch(const std::exception& e)
+        catch (const std::future_error& e)
         {
-            KJ_EXPECT(e.what() == std::string("Future already retrieved"));
+            KJ_EXPECT(e.code() == std::make_error_code(std::future_errc::future_already_retrieved));
         }
     };