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, 11 deletions

diff --git a/tests/specs/install/no_future_install_global/assert.js b/tests/specs/install/no_future_install_global/assert.js
deleted file mode 100644
index c7a6a0680..000000000
--- a/tests/specs/install/no_future_install_global/assert.js
+++ /dev/null
@@ -1,11 +0,0 @@
-const dirs = Deno.readDir("./bins/bin");
-
-let found = false;
-for await (const entry of dirs) {
-  if (entry.name.includes("deno-test-bin")) {
-    found = true;
-  }
-}
-if (!found) {
-  throw new Error("Failed to find test bin");
-}