Pin circleci windows executor (#650)

## Usage and product changes
Pins the executor used for windows jobs in CircleCI to a specific image so updates don't break the pipeline.

.circleci/config.yml

@@ -46,6 +46,11 @@ executors:
     resource_class: macos.m1.medium.gen1
     working_directory: ~/typedb-driver
 
+  win-x86_64:
+    resource_class: windows.xlarge
+    machine:
+      image: windows-server-2022-gui:2024.01.1
+    shell: cmd.exe
 
 commands:
 
@@ -578,10 +583,7 @@ jobs:
       - deploy-dotnet-runtime-snapshot-unix
 
   deploy-snapshot-windows-x86_64:
-    executor:
-      name: win/default
-      size: xlarge
-      shell: cmd.exe
+    executor: win-x86_64
     working_directory: ~/typedb-driver
     steps:
       - checkout
@@ -669,10 +671,7 @@ jobs:
       - test-dotnet-snapshot-mac-rosetta
 
   test-snapshot-windows-x86_64:
-    executor:
-      name: win/default
-      size: xlarge
-      shell: cmd.exe
+    executor: win-x86_64
     working_directory: ~/typedb-driver
     steps:
       - checkout
@@ -748,10 +747,7 @@ jobs:
       - deploy-dotnet-runtime-release-unix
 
   deploy-release-windows-x86_64:
-    executor:
-      name: win/default
-      size: xlarge
-      shell: cmd.exe
+    executor: win-x86_64
     working_directory: ~/typedb-driver
     steps:
       - checkout

RELEASE_NOTES_LATEST.md

@@ -81,7 +81,7 @@ Compiled distributions comprising headers and shared libraries available at: htt
 
 
 ## New Features
-- **Copy jin library from input stream rather than file**
+- **Copy jni library from input stream rather than file**
   We now copy the jni library by reading from it as an input stream rather than as a file copy. This approach works when the JNI jars are nested, such as in Spring Boot projects.