fix(@angular-devkit/build-angular): update list of known tailwind configuration files

With this change we added `tailwind.config.mjs` and `tailwind.config.ts` to known tailwind config files.

Closes #24943

Author: alan-agius4

packages/angular_devkit/build_angular/src/builders/browser-esbuild/options.ts

@@ -203,14 +203,19 @@ export async function normalizeOptions(
   };
 }
 
+/** The list of valid config files can be found https://github.com/tailwindlabs/tailwindcss/blob/ba5454543e74a6d702ce11b410d27672c2ee4b3f/src/util/resolveConfigPath.js#L4-L9*/
+const tailwindConfigFiles = [
+  './tailwind.config.js',
+  './tailwind.config.cjs',
+  './tailwind.config.mjs',
+  './tailwind.config.ts',
+];
+
 function findTailwindConfigurationFile(
   workspaceRoot: string,
   projectRoot: string,
 ): string | undefined {
   // A configuration file can exist in the project or workspace root
-  // The list of valid config files can be found:
-  // https://github.com/tailwindlabs/tailwindcss/blob/8845d112fb62d79815b50b3bae80c317450b8b92/src/util/resolveConfigPath.js#L46-L52
-  const tailwindConfigFiles = ['tailwind.config.js', 'tailwind.config.cjs'];
   for (const basePath of [projectRoot, workspaceRoot]) {
     for (const configFile of tailwindConfigFiles) {
       // Project level configuration should always take precedence.