feat(ngsw): per-locale ngsw.json when --localize is set (#148)

[lukekania]

Summary

Closes #148.

A localized build (--localize) with serviceWorker: true previously skipped ngsw.json generation entirely, with the warning "per-locale manifests are not yet supported". Apps had to choose between i18n and PWA caching.

This change:

• Moves the service-worker step to run after locale fan-out (fan_out_locales).
• When --localize is set, emits one ngsw.json per <out_dir>/<locale>/ subdirectory — each locale subdir is its own PWA deploy root, matching @angular/service-worker's expectation of one manifest per deploy root.
• Asset hashes are computed from each locale's own tree, so a translated bundle hashes differently per locale (correct cache invalidation). Manifest URLs are locale-root-relative (no /<locale>/ prefix).
• The non-localized path is unchanged.
• Drops the skip warning.

No ngsw.rs changes were needed: generate_manifest already walks a dist_dir and emits root-relative URLs, so it works correctly when handed a locale subdir.

Bumps version to 0.10.14.

Test plan

• cargo test -p ngc-rs test_service_worker_pipeline — new test_service_worker_pipeline_localized_fixture plus the existing non-localized fixture pass
• cargo test -p ngc-rs — full crate suite green
• cargo clippy -p ngc-rs --bins --tests — no warnings
• New test asserts: per-locale ngsw.json exists, URLs are deploy-root-relative, hashes match each locale's own bytes, and en/fr record different hashes for the translated bundle