refactor: loosen experimental warnings types

As is, the `browser` and `browser-esbuild` schemas needed to be identical to check for unsupported properties. This loosens it slightly by casting the `browser-esbuild` schema into the `browser` schema and looking for invalid properties. This makes the module more flexible as the `browser-esbuild` schema evolves _and_ more closely aligns with the actual mistake of users who incorrectly think of `browser-esbuild` as supporting all the options of `browser`, which it does not yet do so.

(cherry picked from commit 2d0943d)

Author: dgp1130

packages/angular_devkit/build_angular/src/builders/browser-esbuild/experimental-warnings.ts

@@ -8,6 +8,7 @@
 
 import { BuilderContext } from '@angular-devkit/architect';
 import { Schema as BrowserBuilderOptions } from '../browser/schema';
+import { Schema as BrowserEsbuildOptions } from './schema';
 
 const UNSUPPORTED_OPTIONS: Array<keyof BrowserBuilderOptions> = [
   'budgets',
@@ -30,7 +31,7 @@ const UNSUPPORTED_OPTIONS: Array<keyof BrowserBuilderOptions> = [
   'webWorkerTsConfig',
 ];
 
-export function logExperimentalWarnings(options: BrowserBuilderOptions, context: BuilderContext) {
+export function logExperimentalWarnings(options: BrowserEsbuildOptions, context: BuilderContext) {
   // Warn about experimental status of this builder
   context.logger.warn(
     `The esbuild browser application builder ('browser-esbuild') is currently experimental.`,
@@ -39,7 +40,7 @@ export function logExperimentalWarnings(options: BrowserBuilderOptions, context:
   // Validate supported options
   // Currently only a subset of the Webpack-based browser builder options are supported.
   for (const unsupportedOption of UNSUPPORTED_OPTIONS) {
-    const value = options[unsupportedOption];
+    const value = (options as unknown as BrowserBuilderOptions)[unsupportedOption];
 
     if (value === undefined || value === false) {
       continue;