fix(angular): update angular config to export ui library config

[colinscz]

🔗 Linked issue

Closes #566

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

update angular config to export ui library config for testing purposes
replace outdated appInitializer with provideAppInitializer function

[github-actions]

File	Coverage
All files	92%	✅
www/build/src/components/six-breadcrumbs/six-breadcrumbs.tsx	83%	✅
www/build/src/components/six-button/six-button.tsx	91%	✅
www/build/src/components/six-checkbox/six-checkbox.tsx	93%	✅
www/build/src/components/six-date/calendar-grid.ts	93%	✅
www/build/src/components/six-date/six-date.tsx	96%	✅
www/build/src/components/six-date/components/month-selection.tsx	90%	✅
www/build/src/components/six-date/components/year-selection.tsx	91%	✅
www/build/src/components/six-details/six-details.tsx	98%	✅
www/build/src/components/six-dialog/six-dialog.tsx	98%	✅
www/build/src/components/six-dropdown/six-dropdown.tsx	94%	✅
www/build/src/components/six-error-page/six-error-page.tsx	91%	✅
www/build/src/components/six-file-upload/six-file-upload.tsx	95%	✅
www/build/src/components/six-group-label/six-group-label.tsx	83%	✅
www/build/src/components/six-icon/six-icon.tsx	66%	✅
www/build/src/components/six-icon-button/six-icon-button.tsx	90%	✅
www/build/src/components/six-input/six-input.tsx	97%	✅
www/build/src/components/six-item-picker/six-item-picker.tsx	99%	✅
www/build/src/components/six-menu/six-menu.tsx	80%	✅
www/build/src/components/six-menu-item/six-menu-item.tsx	99%	✅
www/build/src/components/six-paginator/six-paginator.tsx	90%	✅
www/build/src/components/six-picto/six-picto.tsx	66%	✅
www/build/src/components/six-progress-ring/six-progress-ring.tsx	75%	✅
www/build/src/components/six-range/six-range.tsx	92%	✅
www/build/src/components/six-rating/six-rating.tsx	96%	✅
www/build/src/components/six-search-field/six-search-field.tsx	90%	✅
www/build/src/components/six-select/six-select.tsx	88%	✅
www/build/src/components/six-select/util.ts	75%	✅
www/build/src/components/six-sidebar/six-sidebar.tsx	92%	✅
www/build/src/components/six-sidebar-item-group/six-sidebar-item-group.tsx	95%	✅
www/build/src/components/six-switch/six-switch.tsx	95%	✅
www/build/src/components/six-tab/six-tab.tsx	91%	✅
www/build/src/components/six-tab-group/six-tab-group.tsx	78%	✅
www/build/src/components/six-textarea/six-textarea.tsx	88%	✅
www/build/src/components/six-tile/six-tile.tsx	83%	✅
www/build/src/components/six-tooltip/six-tooltip.tsx	94%	✅
www/build/src/functional-components/form-control/form-control.tsx	90%	✅
www/build/src/utils/animation.ts	88%	✅
www/build/src/utils/error-messages.ts	84%	✅
www/build/src/utils/event-listeners.ts	91%	✅
www/build/src/utils/execution-control.ts	90%	✅
www/build/src/utils/focus-visible.ts	83%	✅
www/build/src/utils/icon.ts	92%	✅
www/build/src/utils/modal.ts	75%	✅
www/build/src/utils/popover.ts	83%	✅
www/build/src/utils/scroll.ts	87%	✅
www/build/src/utils/slot.ts	90%	✅

Minimum allowed coverage is 0%

Generated by 🐒 cobertura-action against 485d8a7

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@six-group/ui-library@567

npm i https://pkg.pr.new/@six-group/ui-library-react@567

npm i https://pkg.pr.new/@six-group/ui-library-vue@567

npm i https://pkg.pr.new/@six-group/ui-library-angular@567

commit: 485d8a7

[pennal]

I have two questions:

1. Does this create any breaking issues? Although I don't believe anyone worked around it in any way, should we add something about it in the release docs?
2. Does this change the setup of the lib in the "production" code? or does it affect only the tests?

Other than that, if the CI is clean I think we can confidently merge it

[pennal]

I have two questions:

1. Does this create any breaking issues? Although I don't believe anyone worked around it in any way, should we add something about it in the release docs?

2. Does this change the setup of the lib in the "production" code? or does it affect only the tests?

Other than that, if the CI is clean I think we can confidently merge it

Clarified this offline, it should (and does) not break anything. LGTM