ci: add lumberjack-ivy CI workflow

[LayZeeDK]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Lumberjack is a View Engine-compiled package.

Issue Number: N/A

What is the new behavior?

A separate Lumberjack bundle with partial Ivy compilation is created. This enables faster compilation time for end-users but requires Angular CLI >=11.1. Technically it's fully Ivy-compiled because Lumberjack doesn't contain components.

This package could be published in parallel to @ngworker/lumberjack using a name such as @ngworker/lumberjack-ivy or @ngworker/lumberjack-angular-linker.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[LayZeeDK]

Waiting for ngworker/angular-versions-action#22.

[NachoVazquez]

This is very exciting.

[NachoVazquez]

That version should not be failing. Is that a regression?

[LayZeeDK]

That version should not be failing. Is that a regression?

I updated the dependencies and removed @angular-devkit/build-ng-packagr. We then get errors because of ngworker/angular-versions-action#22.

[LayZeeDK]

We might want to look into the schematics e2e setup to make sure it's reusing the package build artifact and not re-building the schematics sub-package for different versions of Angular.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication