feat: Enhance APIs with file URL path support

[mitsuki31]

Summary

This pull request brings new features, enhance the functionality APIs, improve documentation, and ensure compatibility across different environments.

Notable Changes

• Implemented an internal function to convert file URLs. This function behaves similarly to NodeJS' url.fileURLToPath function but with added support for relative paths. It throws an URIError for non-file protocols or invalid path structures. This function will be utilized in ls* functions to support file URL paths.
• Improved and updated the documentation for the APIs. Additionally, a history section has been added to document changes in each version.
• Added support for file URLs in all ls* functions. Now, these functions can accept string URL paths or URL objects with the 'file:' protocol. However, please note that only the 'file:' protocol is currently supported for directory resolution and listing.
• Fixed an issue with absolute path resolution on Windows systems. The resolution process now ensures that the path passed to fs.readdir adheres to the required format.
• Included several assert functions from the node:assert module to enhance test coverage.
• Added new test cases to ensure the correct behavior of the APIs regarding file URL paths and URL objects with the 'file:' protocol. Also, tests have been added to verify that an URIError is correctly thrown when unsupported protocols are used.

Description

New Features

This pull request brings a new feature to all ls* functions, that is a support to file URL path for dirpath parameter. It accepts both a string URL path or a URL object by following the 'file:' protocol, utilizing an internal function called fileUrlToPath to convert the file URLs.

"Why don't use the inbuilt function provided by Node.js itself?" Well, this function might behave the same with url.fileURLToPath function from node:url module, but this function are supports relative paths. Unlike url.fileURLToPath inbuilt function that doesn't accepts a string URL with relative path, attempting to do so will causing an error.

Here's some examples on how to use the new feature:

// List all files in 'fooBar' directory relative from current directory
lsFiles('file:./fooBar').then(entries => console.log(entries));

const path = require('node:path');
const { pathToFileURL } = require('node:url');
// ESM: import * as path from 'node:path';
//      import { pathToFileURL } from 'node:url';

// List all installed packages inside 'node_modules' directory
ls(pathToFileURL(path.posix.resolve('node_modules')), {
  recursive: false,
  exclude: /\.bin/
}, lsTypes.LS_D).then(entries => console.log(entries));

This new feature has been tested and the tests code are available in the project. If having any issues while using the feature, report to us by providing the issue details.

Test Environments

Introduced new test cases to ensure that the APIs correctly handle file URL paths and URL objects with the 'file:' protocol and also ensured that the APIs throws a URIError when provided with URL paths using unsupported protocols.

Documentation

Added a history section to document changes made to the APIs in each version and improved the documentation for the APIs.

[mitsuki31]

Not a breaking changes, but I desired to make these changes and the new features to be a part of major update.