feat(@angular-devkit/build-angular): Add progress reporters for webpack builds

[GingerGeek]

• Add progress reporters for webpack builds. Previously only the default webpack progress handler was used. The default handler did not display well in all CI environments as it attempted to use the same console line for all progress updates.
• Add simple progress report, logging on new lines each time the build stage or build % changes.
• Add verbose progress report, logging on new lines on every progress update with additional data provided by webpack.
• Change default behaviour on non TTY consoles to use the simple progress report over the current behaviour of no progress reporting, this gives visibility over the status of build.

Previews

default-webpack

Delegate to default handler within ProgressPlugin in webpack (existing behaviour)

simple-color

Logging on new lines each time the build stage or build percentage changes (w/ colour)

verbose-color

Logging on new lines on every progress update with additional data provided by webpack (w colour)

simple-plain

Logging on new lines each time the build stage or build percentage changes (w/o colour)

verbose-plain

Logging on new lines on every progress update with additional data provided by webpack (w/o colour)

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[GingerGeek]

@googlebot CLA should be sorted!

[mgechev]

@GingerGeek this is a large change and we should discuss further if we can merge it.

For such big changes, I'd recommend you to first open an issue so we can discuss if this is in the scope of the project.

[GingerGeek]

@mgechev Apologies, I've created an issue to discuss this further: #13426

[mgechev]

There are quite a few merge conflicts here and this PR has been open since January. Let's close it for now and keep the discussion in #13426. When we agree how to proceed forward, we can go with another PR.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}