feat(angular): support tailwind.config.cjs as valid config file in library executors

[leosvelperez]

Current Behavior

The library executors don't pick up the Tailwind CSS configuration file if named as tailwind.config.cjs which is supported by Tailwind CSS (https://github.com/tailwindlabs/tailwindcss/blob/master/src/util/resolveConfigPath.js#L46).

Expected Behavior

The library executors should auto-detect a tailwind.config.cjs file when used.

Related Issue(s)

Fixes #

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 6a74985. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 11 targets

• nx affected --target=e2e --base=0844ab97e6ea0bb0bba0370ead846e6b0470a7dd --head=6a74985ad02ef7ce0dd0bf30db3400e5314cb705 --exclude=e2e-storybook,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=lint --base=0844ab97e6ea0bb0bba0370ead846e6b0470a7dd --head=6a74985ad02ef7ce0dd0bf30db3400e5314cb705 --parallel=3
• nx affected --target=build --base=0844ab97e6ea0bb0bba0370ead846e6b0470a7dd --head=6a74985ad02ef7ce0dd0bf30db3400e5314cb705 --parallel=3
• nx affected --target=test --base=0844ab97e6ea0bb0bba0370ead846e6b0470a7dd --head=6a74985ad02ef7ce0dd0bf30db3400e5314cb705 --parallel=1
• nx-cloud record -- yarn nx workspace-lint
• nx-cloud record -- yarn documentation
• nx build typedoc-theme
• nx-cloud record -- yarn depcheck
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn nx format:check --base=0844ab97e6ea0bb0bba0370ead846e6b0470a7dd --head=6a74985ad02ef7ce0dd0bf30db3400e5314cb705
• nx-cloud record -- yarn check-imports

---

Sent with 💌 from NxCloud.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated
nx-dev	⬜️ Ignored (Inspect)		May 31, 2022 at 2:10PM (UTC)

[Coly010]

LGTM!

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.