chore(changelog): add fragment for the getExecutor async-drift test fix

The R0.3 executor-registry refactor (#11220) made getExecutor() async;
this new test (#11708) predates that and called it synchronously,
producing a TypeError (getExecutor(...).getProvider is not a function)
instead of the intended assertion.

changelog.d/fixes/11708-gemini-web-retirement-test-async-getexecutor.md

@@ -0,0 +1 @@
+- **fix(tests):** the new Gemini Web Images retirement test (#11708) called the now-async `getExecutor()` synchronously, throwing `TypeError: getExecutor(...).getProvider is not a function` instead of asserting Gemini Web chat stays available. Awaited to match the R0.3 executor-registry refactor (#11220).

tests/unit/gemini-web-image-retirement.test.ts

@@ -111,9 +111,9 @@ test("Gemini Web image-only parser and handler artifacts are retired", () => {
   );
 });
 
-test("Gemini Web chat and legitimate Gemini image providers remain available", () => {
+test("Gemini Web chat and legitimate Gemini image providers remain available", async () => {
   assert.equal(hasSpecializedExecutor("gemini-web"), true);
-  assert.equal(getExecutor("gemini-web").getProvider(), "gemini-web");
+  assert.equal((await getExecutor("gemini-web")).getProvider(), "gemini-web");
   assert.equal(REGISTRY["gemini-web"]?.executor, "gemini-web");
   assert.deepEqual(
     REGISTRY["gemini-web"]?.models.map(({ id }) => id),