This change adds a tool that identifies the next steps for migrating a
project file or directory to Zoneless or OnPush. The priorities for
migration are:

1. Find and report any unsupported uses of ZoneJS APIs. These are easily
   verifiable. If they exist, they need to be removed and the tool
   provides suggested replacements
2. Provide requirements for OnPush compatibility for any files with a
   Component. It is suggested to use an explicit `ChangeDetectionStrategy.Default`
   until it can be verified the migration is complete. The tool skips
   any components with explicit change detection strategy definitions.
   This is required since we have no way of statically verifying a
   component is compatible with OnPush, so we need some way to indicate
   the tool should move on from a component
3. When nothing is identified in the above two steps, move on to test
   files and suggest migrating those to use zoneless. This is the best
   method to verify that components are zoneless compatible.