Update ava to 4.3.3

The [release notes](https://github.com/avajs/ava/releases/tag/v4.3.3)
mention compatibility with Node 18.8.

node_modules/is-unicode-supported/index.js

@@ -1,12 +1,15 @@
+import process from 'node:process';
+
 export default function isUnicodeSupported() {
 	if (process.platform !== 'win32') {
 		return process.env.TERM !== 'linux'; // Linux console (kernel)
 	}
 
-	return Boolean(process.env.CI) ||
-		Boolean(process.env.WT_SESSION) || // Windows Terminal
-		process.env.ConEmuTask === '{cmd::Cmder}' || // ConEmu and cmder
-		process.env.TERM_PROGRAM === 'vscode' ||
-		process.env.TERM === 'xterm-256color' ||
-		process.env.TERM === 'alacritty';
+	return Boolean(process.env.CI)
+		|| Boolean(process.env.WT_SESSION) // Windows Terminal
+		|| process.env.ConEmuTask === '{cmd::Cmder}' // ConEmu and cmder
+		|| process.env.TERM_PROGRAM === 'vscode'
+		|| process.env.TERM === 'xterm-256color'
+		|| process.env.TERM === 'alacritty'
+		|| process.env.TERMINAL_EMULATOR === 'JetBrains-JediTerm';
 }

node_modules/is-unicode-supported/package.json

@@ -1,6 +1,6 @@
 {
   "name": "is-unicode-supported",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Detect whether the terminal supports Unicode",
   "license": "MIT",
   "repository": "sindresorhus/is-unicode-supported",
@@ -36,8 +36,8 @@
     "detection"
   ],
   "devDependencies": {
-    "ava": "^3.15.0",
-    "tsd": "^0.14.0",
-    "xo": "^0.38.2"
+    "ava": "^4.0.1",
+    "tsd": "^0.19.1",
+    "xo": "^0.47.0"
   }
 }

node_modules/is-unicode-supported/readme.md

@@ -8,8 +8,8 @@ Note that the check is quite naive. It just assumes all non-Windows terminals su
 
 ## Install
 
-```
-$ npm install is-unicode-supported
+```sh
+npm install is-unicode-supported
 ```
 
 ## Usage