feat: new js apis

[amrbashir]

closes #2233
closes #4490
closes #4350

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

Although some of the APIs intended in this PR could be add in a minor version of v1, The majority will be breaking changes so it is better to just include all in one PR for v2. I will also try to split the PR into a reviewable chunks.

TODOS:

1. os module

   • Remove type()
   • Adjust platform() to match Rust's implementation.
   • hostname()
   • Rename tempdir() to tempDir()

2. path module

   • tempDir()

3. fs module

   • create()
   • open()
   • close()
   • FsFile class
     • close()
     • read()
     • write()
     • seek()
     • truncate()
     • stat()
   • write()
   • writeFile()
   • writeTextFile()
   • Remove writeBinaryFile()
   • read()
   • readFile()
   • readTextFile()
   • readTextFileLines()
   • Remove readBinaryFile()
   • Adjust copyFile()
   • Adjust readDir()
   • mkdir()
   • remove()
   • rename()
   • seek()
   • truncate()
   • ftruncate()
   • stat()
   • lstat()
   • fstat()

4. http module

   • Make fetch compatible with the web api
     • stream file:// on reqwest-client feature
     • cancel fetch using AbortController
   • Remove Client and getClient

5. window module

   • Remove appWindow
   • Combine WindowManager, WebviewHandle and WebViewWindow into one Window class.

• Merge all change files into one big change file

[jlarmstrongiv]

Are fs streaming APIs planned? See #2233 (comment) and #4133

[lucasfernog]

@amrbashir we'll need to find some time to move these to the plugins-workspace repo. I would wait a little longer on the FS APIs, since we'll see if cap-std can help us there (see #6107).

[amrbashir]

sure, I will start on porting them to plugins-workspace this week