Fix Angular 21 upgrade issues: change detection, test mocks, and modal dropdowns

[Copilot]

Angular 21 upgrade broke component initialization, unit tests, and modal dropdowns due to stricter lifecycle rules and new dialog top-layer implementation.

Changes

Component Lifecycle

• Added ChangeDetectorRef.markForCheck() after async data updates in ngOnInit() chains
• Affects: EformsPageComponent, FullLayoutComponent, FooterComponent, EntityEditCreateComponent, NavigationComponent, HeaderComponent, FoldersComponent, EntitySearchComponent, EntitySelectComponent
• Angular 21 enforces stricter change detection during initialization; synchronous detectChanges() in init phase blocks subsequent async operations

Unit Test Compatibility

• Fixed TranslateService mocks with complete interface including getParsedResult(), getCurrentLang(), event emitters
• Added EventEmitter for onLangChange, onTranslationChange, onDefaultLangChange (required by Angular 21's TranslatePipe)
• Affects 22 test files

Property Binding Syntax

• Corrected dropdownPosition from string attribute to property binding: [dropdownPosition]="'bottom'"
• 13 component templates updated

Modal Dropdown Positioning (Partial)

• Added [appendTo]="'.cdk-overlay-pane'" to mtx-select components in modals
• Addresses Angular 21's HTML Dialog API top-layer stacking (elements outside top-layer render behind dialogs)
• 11 modal templates updated
• Note: Positioning calculations still problematic; mtx-select uses Angular Material CDK overlays (not ng-select), may require library update for full Angular 21 compatibility

Known Limitation

mtx-select dropdowns in modals remain imperfectly positioned. Angular 21's native top-layer (via popover="manual") creates new stacking context incompatible with current mtx-select overlay implementation. The appendTo workaround keeps dropdowns visible but positioning relative to input fields is incorrect.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Branch: angular19 - Fixing eerror</issue_title>
<issue_description>On the angular19 branch which is updated to have these errors when loading:

ERROR RuntimeError: NG0100: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: '[]'. Current value: '[{"id":1,"createdAt":"2026-01-29T06:50:55.000Z","updatedAt":null,"label":"sfsfdsf","description":null,"repeated":1,"folderName":null,"workflowState":"created","deployedSites":[],"hasCases":false,"disp…'. Expression location: EformsPageComponent2 component. Find more at https://v21.angular.dev/errors/NG0100
    at throwErrorIfNoChangesMode (_debug_node-chunk.mjs:3475:9)
    at bindingUpdated (_debug_node-chunk.mjs:7918:9)
    at Module.ɵɵproperty (_debug_node-chunk.mjs:14300:7)
    at EformsPageComponent_Template (eforms-page.component.html:98:3)
```</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes Branch: angular19 - Fixing eerror #7484

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[renemadsen]

@copilot rebase or make any smal change, so the github actions pr pipeline is getting triggered

[Copilot]

@copilot rebase or make any smal change, so the github actions pr pipeline is getting triggered

Added a clarifying comment to trigger the CI pipeline. Commit: 04dd2f4