chore(e2e/nx): update dependency ng-packagr to v21.2.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ng-packagr	21.2.0 → 21.2.1

---

Release Notes

ng-packagr/ng-packagr (ng-packagr)

v21.2.1

Compare Source

Bug Fixes

• ensure dts sourcemaps point to original ts files (c324321)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: e2e/nx/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: nx@0.0.0
npm error Found: @angular/compiler-cli@20.3.18
npm error node_modules/@angular/compiler-cli
npm error   dev @angular/compiler-cli@"20.3.18" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler-cli@"^21.0.0 || ^21.2.0-next" from ng-packagr@21.2.0
npm error node_modules/ng-packagr
npm error   dev ng-packagr@"21.2.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-13T10_42_35_114Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-13T10_42_35_114Z-debug-0.log

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (35b7e5f) to head (2210a89).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main    #13048   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          228       228           
  Lines         4168      4168           
  Branches      1187      1187           
=========================================
  Hits          4168      4168           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.