This is finally solved as of today with the release of Angular 20 (because of the update to the critters sub-dependency).

Just update angular by following the guide: https://angular.dev/update-guide

And the subsequent builds will no longer give this warning.