BREAKING: `DENO_FUTURE=1` by default, or welcome to Deno 2.0 (#25213)

This commit effectively turns Deno into Deno 2.0.

This is done by forcing `DENO_FUTURE=1` env var, that was available in
the past few months to try Deno 2 changes.

This commit contains several breaking changes scheduled for Deno 2:
- all deprecated JavaScript APIs are not available any more, mostly
`Deno.*` APIs
- `window` global is removed
- FFI, WebGPU and FS APIs are now stable and don't require
`--unstable-*` flags
- import assertions are no longer supported
- "bring your own node modules" is enabled by default

This is the first commit in a series that are scheduled before the Deno
2 release.

Follow up work is tracked in
https://github.com/denoland/deno/issues/25241.

---------

Co-authored-by: Asher Gomez <ashersaupingomez@gmail.com>
Co-authored-by: Nayeem Rahman <nayeemrmn99@gmail.com>
Co-authored-by: Nathan Whitaker <nathan@deno.com>

1 files changed, 0 insertions, 13 deletions

diff --git a/tests/specs/install/no_future_install_global/__test__.jsonc b/tests/specs/install/no_future_install_global/__test__.jsonc
deleted file mode 100644
index 657cdab80..000000000
--- a/tests/specs/install/no_future_install_global/__test__.jsonc
+++ /dev/null
@@ -1,13 +0,0 @@
-{
-  "tempDir": true,
-  "steps": [
-    {
-      "args": "install --root ./bins --name deno-test-bin ./pkg/main.js",
-      "output": "install.out"
-    },
-    {
-      "args": "run -A ./assert.js",
-      "output": ""
-    }
-  ]
-}