Extracting an archive to a root subfolder fails with ENOENT

Describe the bug

Extracting an archive to a root subfolder fails with NOENT.

Using the following typescript code,

    const tar_path = await tc.downloadTool(SOME_URL);
    const location = "/location";
    core.info(`Archive downloaded to ${tar_path}.`);

    const extract_location = await tc.extractTar(tar_path, location);
    core.info(`Archive extracted to ${extract_location}.`);

a consumer fails with:

Archive downloaded to /home/runner/work/_temp/e87a9e79-45b6-4f14-9d50-6e13043a11c5.
Error: ENOENT: no such file or directory, mkdir

To Reproduce
Steps to reproduce the behavior:

1. Create an action that uses tool cache, downloads an archive and extracts to a root subfolder
2. Create a workflow that uses this action
3. Run this action
4. Error

A github action that suffers from this problem is my WIP setup-watcom.
A consumer of this github action is watcom-cmake.
(The reproducers are currently on the experimental branch. the master branch works around this issue by extracting the toolchain to the current working directory)

This github action log shows the error message.

Expected behavior
The tar is extracted to the root subfolder, and is ready for use.

Screenshots

Additional context
The same action works on Windows, which extracts the toolchain to a direct subfolder of C:\.

The error is not EACCESS, so I think this is not a permission error.

Start by tracing the extractTar entry point used in the TypeScript example and reproduce the failure with an absolute root-subfolder destination. Compare the behavior with the Windows case and the linked action log; done means the archive extracts successfully to the requested root subfolder without ENOENT.