feat(migrations): add migration to remove unclaimed bindings on ng-template - #69718

Context

This is the follow-up to #69640, where unclaimed property bindings on will start producing a compilation error (as discussed with @JeanMeche in that PR). This migration helps existing codebases adopt that change automatically via ng update.

Why the migration removes the bindings instead of fixing them (e.g. adding missing imports)
Before #69640, these bindings were silently ignored by the compiler: they had no effect at runtime. Removing them is therefore a strictly behavior-preserving transformation — the app behaves exactly the same before and after the migration, which is the safest property an automated migration can have.
Trying to "fix" the binding instead (e.g. by adding a missing directive import) would be heuristic and potentially unsafe: we can't reliably know whether the binding was a missing import, a typo, or an input that no longer exists after the directive evolved — all cases that actually showed up in the TGP run for #69640.
The migration diff itself also acts as a signal: if a developer sees a removed binding they actually intended to work, that's their cue to add the proper import — visibility that the silently-ignored binding never gave them.