[native] Fix incorrect initialization of 'folly::Promise' object

Fixes prestodb#26094

For a `folly::Promise` object that is expected to be overwritten, we
should use `folly::makeEmpty()` to initialize it (it is 'invalid')
instead of the default constructor (it will be 'valid' but
'not fulfilled', assigning to it will cause an exception). Creating an
exception triggers a stack unwind, which can saturate the CPU in
high-concurrency scenarios, causing significant performance issues.

We don't need to create a new Promise and destruct the previous one
in the `ResponseHandler::initialize()` function because
`ResponseHandler` isn't supposed to be reused. Therefore, we can
simplify the `ResponseHandler::initialize` method.

Author: lingbin

presto-native-execution/presto_cpp/main/http/HttpClient.cpp

@@ -197,10 +197,7 @@ class ResponseHandler : public proxygen::HTTPTransactionHandler {
   folly::SemiFuture<std::unique_ptr<HttpResponse>> initialize(
       std::shared_ptr<ResponseHandler> self) {
     self_ = self;
-    auto [promise, future] =
-        folly::makePromiseContract<std::unique_ptr<HttpResponse>>();
-    promise_ = std::move(promise);
-    return std::move(future);
+    return promise_.getSemiFuture();
   }
 
   void setTransaction(proxygen::HTTPTransaction* /* txn */) noexcept override {}