Fix Angular integration test timeout by simplifying fixture

[ivanovac]

Problem

The Angular integration test (deploying an angular app) consistently fails due to CF's 15-minute staging timeout.

Timeline from failing test logs:

Stage	Duration
npm install	~5 min
ng build --prod	~7-8 min
Other staging steps	~2 min
Total	~15+ min → TIMEOUT

Root Cause

The angular_dotnet fixture uses Angular 13 with:

• Heavy production build optimizations (tree-shaking, minification, AOT)
• 958 npm packages including unused test/dev dependencies
• Combined staging time exceeds CF's hard 15-minute limit

Solution

1. Use --optimization=false in production build
   Skips expensive minification while still testing production configuration path

2. Remove unused dependencies from package.json:

   • Test deps: karma, jasmine-core, karma-* plugins, @types/jasmine
   • Runtime deps: oidc-client, @angular/platform-server, run-script-os, jquery, popper.js

3. Remove test and serve targets from angular.json

   • Removed test architect target (karma-based testing)
   • Removed serve architect target (dev server with proxy)
   • Removed server architect target (SSR)

4. Remove unused files:

   • karma.conf.js, tsconfig.spec.json, src/test.ts
   • proxy.conf.js, aspnetcore-https.js

5. Regenerate package-lock.json

   • Reduces packages from 958 to 880 (-8%)
   • Reduces vulnerabilities from 92 to 46 (-50%)

Impact

Metric	Before	After
npm packages	958	880
Vulnerabilities	92	46
Estimated staging	~15+ min	~8-10 min

Testing

• Integration tests pass on cflinuxfs4
• Integration tests pass on cflinuxfs5
• App still serves Angular content correctly

Related

• Supersedes/alternative to Fix Angular integration test timeout by using development build #1322

[tnikolova82]

lgtm