💸 Tech Debt - Arbitrary Value Text Colour

Description
Due to build failures where the Tailwind bundler was not building with an @apply text-red-550 in the formGroup.module.css file, I had to change it to @apply text-[#dc3545]. This not ideal, it would be better if the problem was solved with using the custom 550 colour stored in the Tailwind config file.

Proposed solution

• Diagnose why the @apply is not working in the build process
• Change @apply mt-1 hidden w-full text-xs text-[#dc3545]; to @apply mt-1 hidden w-full text-xs text-red-550;
• Change @apply rounded-none border-0 !border-b-[1px] !border-solid !border-[#ccc] bg-transparent py-[6px] pr-[12px] text-[1em] text-[#333] shadow-none; to @apply rounded-none border-0 !border-b-[1px] !border-solid !border-[#ccc] bg-transparent py-[6px] pr-[12px] text-[1em] text-gray-550 shadow-none;
• Consider replacing the CSS module entirely (as it is not the cleanest way of applying Tailwind styles)

Start with formGroup.module.css and the Tailwind config, then reproduce the build failure involving @apply text-red-550. Determine why the custom 550 colours are not resolved, update the listed arbitrary colour utilities, and verify that the Tailwind build succeeds without the CSS module replacement being required.