Client does not exit after invoking .destroy()

[Bullrich]

When running tests the client does not properly exit, keeping the thread running.

This happens even when .destroy() is invoked.

This gives problems with test suites, as they never finish.

It is currently making paritytech/get-fellows-action#11 test fail by timing out.

Minimal reproduction

Test file in src/test/papi.test.ts

import { createClient } from "@polkadot-api/client";
import { getChain } from "@polkadot-api/node-polkadot-provider";
import { WebSocketProvider } from "@polkadot-api/ws-provider/node";

import relayDescriptor from "../codegen/relay";

test("Example", async () => {
  const polkadotClient = createClient(
    getChain({
      provider: WebSocketProvider("wss://rpc.polkadot.io"),
      keyring: [],
    }),
  );

  console.log("Requesting data");
  await polkadotClient
    .getTypedApi(relayDescriptor)
    .query.Identity.IdentityOf.getEntries();
  console.log("Finished operation");

  polkadotClient.destroy();
});

Log result

yarn run v1.22.21
$ jest src/test/papi.test.ts
  console.log
    Requesting data

      at src/test/papi.test.ts:15:11

 FAIL  src/test/papi.test.ts (21.206 s)
  ✕ Example (20003 ms)

  ● Example

    thrown: "Exceeded timeout of 20000 ms for a test.
    Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

       5 | import relayDescriptor from "../codegen/relay";
       6 |
    >  7 | test("Example", async () => {
         | ^
       8 |   const polkadotClient = createClient(
       9 |     getChain({
      10 |       provider: WebSocketProvider("wss://rpc.polkadot.io"),

      at Object.<anonymous> (src/test/papi.test.ts:7:1)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        21.229 s
Ran all test suites matching /src\/test\/papi.test.ts/i.
Jest did not exit one second after the test run has completed.

'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.