test(ci): Pin to 2022.08.1 CircleCI Windows image, rather than "stabl…

…e" (#1846)

Same spirit as apollographql/router#4637

---

CircleCI updated their `current` (also known as `stable`) label to a new
version that was published around the time that our Windows CI tests
started [mysteriously and consistently
failing](https://app.circleci.com/pipelines/github/apollographql/rover/3649/workflows/6c3eb0a4-3805-45ab-af93-22a174db13b3)
on February 8th at approximately 15:00 UTC — much like we observed on
the `router` repository at the same time.

Through logs and conversations with support, we understand this to be
true. To mitigate this and get our builds passing again, we are
hardcoding the builds to the version that we now are able to know with
certainty _was_ working, `windows-server-2019-vs2019:2022.08.1`. The
version which appears to be failing is **at the very least**
`windows-server-2019-vs2019:2023.01.1`, but possibly earlier.

This PR changes the unpinned `stable` tag in our configuration to use
the known-good release and we will then release and iterate _up_ from
there, as much as possible.

.circleci/config.yml

@@ -73,7 +73,7 @@ executors:
 
   amd_windows: &amd_windows_executor
     machine:
-      image: "windows-server-2019-vs2019:stable"
+      image: "windows-server-2019-vs2019:2022.08.1"
     resource_class: windows.xlarge
     shell: powershell.exe -ExecutionPolicy Bypass
     environment: