ref(angular): remove unnecessary devdependencies, minor review changes

Author: Lms24

packages/angular/angular.json

@@ -1,3 +1,4 @@
+/* To learn more about this file see: https://angular.io/guide/workspace-config */
 {
   "$schema": "../../node_modules/@angular/cli/lib/config/schema.json",
   "version": 1,

packages/angular/package.json

@@ -44,10 +44,8 @@
     "@angular/cli": "~10.2.4",
     "@angular/compiler-cli": "~10.2.5",
     "@types/node": "^12.11.1",
-    "codelyzer": "^6.0.0",
     "ng-packagr": "^10.1.0",
     "ts-node": "~8.3.0",
-    "tslint": "~6.1.0",
     "typescript": "~4.0.2",
     "zone.js": "~0.10.2"
   },

packages/angular/tsconfig.ngc.json

@@ -17,10 +17,12 @@
     "strictMetadataEmit": true,
     "enableResourceInlining": true,
     // As per Angular 10, the recommendation from the library creation guide
-    // is to disable compilation for Ivy in production builds to ensure
-    // compatibility with Angular 10.
-    // For Angular 11-13 applications, ngcc and the Angular linker ensure that
-    // the library code is processed to match the specific Angular runtime version.
+    // is to disable compilation for the Ivy rendering engine in production builds
+    // to ensure compatibility with Angular 10.
+    // For Angular 11-13 applications, ngcc and the Angular linker convert the compiled JS
+    // at application compile time into an Ivy-compatible version which is then further used in
+    // the build process. This ensures compatibility with newer Angular versions than the one
+    // that was used to initially compile the library (Angular 10 in our case).
     "enableIvy": false
   }
 }