chore: scan duo-ui components for tailwind utilities to bundle
Description
Updated our VSCode tailwind config to also scan duo-ui components for tailwind utility classes to include in our bundle.
This is required because the newer versions of gitlab-ui have removed duo-ui components, and so these utility classes are no longer picked up.
Related Issues
Resolves #1756 (closed)
How has this been tested?
-
If src/browserorsrc/commonhas been modified, please consider interoperability with the Web IDE. See Running the Extension in WebIDE. -
Consider an end-to-end test for significant new features that aren't covered by integration tests.
Screenshots (if appropriate)
What CHANGELOG entry will this MR create?
-
fix:Bug fix fixes - a user-facing issue in production - included in changelog -
feature:New feature - a user-facing change which adds functionality - included in changelog -
BREAKING CHANGE:(fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog -
None - other non-user-facing changes