feat@angular-devkit/build-angular: allow TS config files for tailwindcss

[burner-account]

as mostly the filepath is passed around and handed off to tailwindcss, this might work

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• [ x] The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

Issue Number: #24943

What is the new behavior?

The behavior is unchanged, only now one more value "tailwind.config.ts" is deemed valid to pass through to tailwindcss.
(see ./packages/angular_devkit/build_angular/src/builders/browser-esbuild/css-plugin.ts)

Does this PR introduce a breaking change?

• Yes
• [ x] No

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[burner-account]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

I will not sign up with google to fill out a CLA. If there is an option to sign the CLA without creating a google account, please be so kind and let me know.

[alan-agius4]

@burner-account, thanks for your contribution but a Google account is required to sign the CLA.

Closing since your are not willing to create a Google account.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}