fix(journey-client,device-client): fix AbortSignal cross-realm failure on Node 24

Node 24 tightened undici's instanceof AbortSignal check. When vitest runs
under jsdom, RTK's createAsyncThunk picks up jsdom's AbortController, producing
a signal that fails instanceof in native fetch.

Switch both store test files to @vitest-environment node. The redirect test
that needed window.location.assign is updated to use vi.stubGlobal instead
of vi.spyOn so it works without a DOM environment.

Author: ryanbas21

packages/device-client/src/lib/device.store.test.ts

@@ -1,3 +1,4 @@
+// @vitest-environment node
 /*
  * Copyright (c) 2025 Ping Identity Corporation. All rights reserved.
  *

packages/journey-client/src/lib/client.store.test.ts

@@ -1,3 +1,4 @@
+// @vitest-environment node
 /*
  * Copyright (c) 2025 Ping Identity Corporation. All rights reserved.
  *
@@ -204,10 +205,7 @@ describe('journey-client', () => {
     };
     const step = createJourneyStep(mockStepPayload);
     const assignMock = vi.fn();
-    const locationSpy = vi.spyOn(window, 'location', 'get').mockReturnValue({
-      ...window.location,
-      assign: assignMock,
-    });
+    vi.stubGlobal('window', { location: { assign: assignMock } });
     setupMockFetch();
 
     const client = await journey({ config: mockConfig });
@@ -216,7 +214,7 @@ describe('journey-client', () => {
     expect(mockStorageInstance.set).toHaveBeenCalledWith({ step: step.payload });
     expect(assignMock).toHaveBeenCalledWith('https://sso.com/redirect');
 
-    locationSpy.mockRestore();
+    vi.unstubAllGlobals();
   });
 
   describe('resume()', () => {