feat(@schematics/angular): stabilize refactor-jasmine-vitest schematic

[hawkgs]

Stabilize refactor-jasmine-vitest schematic by covering the known remaining test patterns and cases.

The current state of the schematic covers the most common and used test patterns. This PR adds rather peripheral API to the list of supported transformations. Most of these do not have a Vitest equivalent.

API	State
jasmine.createSpy('withName')	✅ Added support
spy.calls.thisFor(index)	✅ Added support
spy.calls.saveArgumentsByValue()	🚧 Not supported; Comment added
spy.and.identity()	✅ Added support
.and.returnValue(Promise.resolve(x)) / .and.returnValue(Promise.reject(x))	✅ Added support
fail(new Error())	✅ Added support
jasmine.clock().withMock()	🚧 Not supported; Comment added
jasmine.clock().autoTick()	🚧 Not supported; Comment added
jasmine.addAsyncMatchers()	🚧 Not supported; Comment added
jasmine.addSpyStrategy()	🚧 Not supported; Comment added
jasmine.addCustomObjectFormatter()	🚧 Not supported; Comment added
toBeNullish()	✅ Added support
throwUnless() / throwUnlessAsync()	🚧 Not supported; Comment added
getSpecProperty()	🚧 Not supported; Comment added
jasmine.MAX_PRETTY_PRINT_DEPTH / MAX_PRETTY_PRINT_CHARS / MAX_PRETTY_PRINT_ARRAY_LENGTH	🚧 Not supported; Comment added

[gemini-code-assist]

Code Review

This pull request expands the Jasmine to Vitest migration schematics by adding support for several Jasmine APIs, including toBeNullish, createSpy, and various spy strategies. It also introduces TODO comments for unsupported Jasmine features and improves existing transformations for fail() and spy call inspections. Feedback was provided to improve the toBeNullish transformation by using loose equality to avoid double evaluation of expressions with side effects, and to use the TypeScript factory API for numeric literals in transformThisFor for better consistency.

[clydin]

This PR was merged into the repository. The changes were merged into the following branches:

• main: de630c2