Latest Angular Version Supported with AEM SPA

One of My Customers using AEM Cloud Service and setup the AEM Project with ui.frontend module with “angular”.
By Default, ui.frontend module comes with Angular Version 9.
However the Customer is looking to use Angular Version 16 and hence they have followed the Angular Upgrade Guide[1]
[1]- https://update.angular.io/?v=9.0-10.0
The Team is able to upgrade the version to 12 successfully but while doing the upgrade to 13 they are getting below Errors while building the AEM Project.

> npm ERR! code ERESOLVE
> npm ERR! ERESOLVE could not resolve
> npm ERR!
> npm ERR! While resolving: @adobe/aem-angular-editable-components@1.4.0
> npm ERR! Found: @angular/common@13.4.0
> npm ERR! node_modules/@angular/common
> npm ERR! peer @angular/common@"13.4.0" from @angular/forms@13.4.0
> npm ERR! node_modules/@angular/forms
> npm ERR! @angular/forms@"~13.4.0" from the root project
> npm ERR! peer @angular/common@"13.4.0" from @angular/platform-browser@13.4.0
> npm ERR! node_modules/@angular/platform-browser
> npm ERR! peer @angular/platform-browser@"13.4.0" from @angular/forms@13.4.0
> npm ERR! node_modules/@angular/forms
> npm ERR! @angular/forms@"~13.4.0" from the root project
> npm ERR! peer @angular/platform-browser@"13.4.0" from @angular/platform-browser-dynamic@13.4.0
> npm ERR! node_modules/@angular/platform-browser-dynamic
> npm ERR! @angular/platform-browser-dynamic@"~13.4.0" from the root project
> npm ERR! 2 more (@angular/router, the root project)
> npm ERR! 3 more (@angular/platform-browser-dynamic, @angular/router, the root project)
> npm ERR!
> npm ERR! Could not resolve dependency:
> npm ERR! peer @angular/common@"^9.1.9" from @adobe/aem-angular-editable-components@1.4.0
> npm ERR! node_modules/@adobe/aem-angular-editable-components
> npm ERR! peer @adobe/aem-angular-editable-components@"^1.0.3" from @adobe/aem-core-components-angular-spa@1.0.8
> npm ERR! node_modules/@adobe/aem-core-components-angular-spa
> npm ERR! @adobe/aem-core-components-angular-spa@"^1.0.8" from the root project
> npm ERR! @adobe/aem-angular-editable-components@"^1.2.0" from the root project
> npm ERR!
> npm ERR! Conflicting peer dependency: @angular/common@9.1.13
> npm ERR! node_modules/@angular/common
> npm ERR! peer @angular/common@"^9.1.9" from @adobe/aem-angular-editable-components@1.4.0
> npm ERR! node_modules/@adobe/aem-angular-editable-components
> npm ERR! peer @adobe/aem-angular-editable-components@"^1.0.3" from @adobe/aem-core-components-angular-spa@1.0.8
> npm ERR! node_modules/@adobe/aem-core-components-angular-spa
> npm ERR! @adobe/aem-core-components-angular-spa@"^1.0.8" from the root project
> npm ERR! @adobe/aem-angular-editable-components@"^1.2.0" from the root project
> npm ERR!
> npm ERR! Fix the upstream dependency conflict, or retry
> npm ERR! this command with --force, or --legacy-peer-deps
> npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Just wanted to confirm if the latest AEM Archetype is compatible with which Angular version.
Is it expected to work with Angular Version 16?
Also, I can see there is an open issue on GitHub where the customer is trying to upgrade the angular version to 13.
https://github.com/adobe/aem-angular-editable-components/issues/65

Start by checking the latest AEM archetype package manifests and the peer-dependency declarations for @adobe/aem-angular-editable-components and @adobe/aem-core-components-angular-spa. Reproduce the reported npm resolution failure while upgrading from Angular 12 to 13, then determine and document the supported Angular version and whether Angular 16 is compatible, considering linked issue #65.

Written by the indexing model from the issue text.