fix(tests): Complete Vitest migration fixes for CI compilation errors

[Copilot]

The automated Vitest migration schematic left several compatibility issues that caused CI compilation failures.

Changes

• Vitest API migration

  • Added missing expect import to test utilities
  • Replaced jasmine.getEnv().beforeEach/afterEach with Vitest's top-level hooks
  • Replaced jasmine.createSpyObj with manual mock objects using vi.fn()
  • Replaced pending() with it.skip() for skipped tests

• Assertion syntax

  • Moved custom error messages before matchers: expect(value, 'message').toBe(expected) instead of expect(value).toBe(expected, 'message')

• Type corrections

  • Replaced string literals with proper enums: GridPagingMode.Remote, GridSelectionMode.none, GridColumnDataType.*
  • Added missing component properties referenced in templates (isEditable, isHidden, isGroupable, paging)

• Deprecated API cleanup

  • Removed deprecated grid properties: exportExcel, exportCsv, moveable
  • Fixed mock emitter types using any for TypeScript compatibility

Example

// Before - Jasmine API
(jasmine.getEnv() as any).beforeEach(() => { /* ... */ });
const spy = jasmine.createSpyObj<T>(methods);
expect(value).toBe(expected, 'error message');

// After - Vitest API
beforeEach(() => { /* ... */ });
const spy: any = { method: vi.fn() };
expect(value, 'error message').toBe(expected);

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.