Description

Migrate library schematic test setup from Karma/Jasmine to Vitest and Angular standalone testing. Removed Karma config and legacy test.ts templates, added src/test-setup.ts templates that initialize Angular testing with zone.js/testing and BrowserTestingModule. Updated tsconfig.lib.json to exclude src/test-setup.ts and tsconfig.spec.json to use "vitest/globals" types and simplified include/files. Adjusted generate-lib to use a UnitTest builder with a vitest runner and buildTarget instead of Karma-specific options, and added UnitTest to Builders enum.

Resolves #24714 (write the related issue number if available)

How to test it?

How to test it?

1. Build the schematics package:

   • Go to abp/npm/ng-packs
   • Run:

     npm run build:schematics

2. Link the built schematics package locally:

   • Go to abp/npm/ng-packs/dist/packages/schematics
   • Run:

     npm link

3. Link @abp/ng.schematics into the template project:

   • Go to volo/abp/templates/module/angular
   • Run:

     npm link @abp/ng.schematics

4. Run the generator:

   • Still in volo/abp/templates/module/angular, run:

     ng generate @abp/ng.schematics:create-lib

5. When prompted, use the following options:

   • Package name: test-full-lib
   • Is secondary entrypoint: No (false)
   • Template type: standalone

6. Run the tests:

   • In volo/abp/templates/module/angular, run:

     yarn test