chore: upgrade deno_core (#22725)

<!--
Before submitting a PR, please read
https://docs.deno.com/runtime/manual/references/contributing

1. Give the PR a descriptive title.

  Examples of good title:
    - fix(std/http): Fix race condition in server
    - docs(console): Update docstrings
    - feat(doc): Handle nested reexports

  Examples of bad title:
    - fix #7123
    - update docs
    - fix bugs

2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't
run
   all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench'
label.
-->

1 files changed, 1 insertions, 2 deletions

diff --git a/ext/fs/30_fs.js b/ext/fs/30_fs.js
index 3858bba26..c2fb66528 100644
--- a/ext/fs/30_fs.js
+++ b/ext/fs/30_fs.js
@@ -72,7 +72,6 @@ import {
   op_fs_utime_sync,
   op_fs_write_file_async,
   op_fs_write_file_sync,
-  op_is_terminal,
   op_set_raw,
 } from "ext:core/ops";
 const {
@@ -769,7 +768,7 @@ class FsFile {
   }
 
   isTerminal() {
-    return op_is_terminal(this.#rid);
+    return core.isTerminal(this.#rid);
   }
 
   setRaw(mode, options = {}) {