feat(schematics): lu-select migration schematic

[Supamiu]

Description

New lu-select schematic to migrate as many lu-select as we can into new simple/multiple selects.

Opening this as a draft because I'm on holidays for 3 weeks this evening and I want to be able to keep track of everything + allow anyone to contribute if they want to.

Here is the goal todo list, with some example cases:

• Migrate basic static lu-select with simple option-picker into lu-simple-select (example: https://github.com/LuccaSA/Lucca.AppStore/blob/b9ea2d9b4154800760ad616a772348fc8f4f8a0c/front/src/app/shared/components/culture-select/translation-orchestrator.component.html#L6-L16 but this one is inside the tests already).
• Migrate custom *luDisplayer into its modern version (ng-container *luDisplayer)
• Migrate custom lu-option rendering into its modern version (ng-container *luOptionDisplayer)
• Migrate lu-establishment-select, lu-user-select or lu-qualification-select into corresponding select with api directive
• Migrate lu-api-select into corresponding select with apiVX directive depending on the standard used
• Migrate cases with lu-option-picker-advanced and simple feeder/option combo: https://github.com/LuccaSA/Timmi.Timesheet/blob/1f95fac02a010cce18933969217d6b5972840454/front/projects/pwa/src/app/pages/settings/pages/rules/components/cumulation-rule/cumulation-rule.component.html#L10-L32
• Migrate input-clearer into clearer on new select
• Migrate complex displayer cases: https://github.com/LuccaSA/Organization.Structure/blob/79e553d1f386496d88ed6bd896e5b67076bf9a0a/front/skills/src/app/pages/skill/add-job-modal/add-job-modal.component.html#L3-L27

Cases we need to filter and add a comment to explain why:

• lu-department-select is a tree picker, we don't have a modern version of this yet
• Any unsupported input/attribute on select (which would, in most cases, indicate that there's some custom behavior going on): https://github.com/LuccaSA/Figgo/blob/5e98f4a4f915bb3cc493c0170751a23663b57195/front/src/app/areas/statutories-workflow-templates/statutory-workflow-template/steps/steps.component.html#L69-L77
• Cases where options are listed in the template as multiple lu-option rows instead of having them in an array inside TS, migrating this would mean parsing and then building the array in TS which might be a bit too complex for now.
• lu-option-select-all cannot be migrated as-is, since the new select-all behavior changes the underlying data model.
• tree-option-picker cannot be migrated, we don't have a modern version of it.
• lu-option with [value] using a nested key in the option value from array
• lu-establishment-select, lu-user-select or lu-qualification-select with their service overrided inside @Component's providers.
• Custom content inside lu-option-picker that's not from LF as direct child of the picker (even just a div, because it means custom panel content and we can't do that): https://github.com/LuccaSA/Cleemy.Banking/blob/0e74c48401564e4d72fdfa8e5e4d02da59abc22e/front/src/components/transactions/components/transactions-filters/transactions-filters.component.html#L30-L42

---

---

[LuccaIntegration]

👩‍🍳 https://lucca-front.lucca.tech/PR-3292/storybook

[LuccaIntegration]

👩‍🍳 https://lucca-front.lucca.tech/PR-3292/storybook

[LuccaIntegration]

👩‍🍳 https://lucca-front.lucca.tech/PR-3292/storybook