Replace Tailwind,HTMX CDN with Local Build.

[anuragSharma1112]

Description

I have removed the Tailwind CDN and set up Tailwind locally with PostCSS. The CSS is now being compiled into src/main/resources/static/css/output.css.

For local development, I run npx tailwindcss -i ./src/main/resources/static/css/input.css -o ./src/main/resources/static/css/output.css --watch to generate output.css.

In production or testing, we don’t need to run this manually — we can automate it:

Either pre-build: we commit the generated output.css file into the repo, so it’s already available after pulling the code.

Or build step: add the Tailwind build command into our Maven build / CI pipeline so output.css is generated automatically during deployment.
Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Database change

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
NA

Checklist:

• I have created ADR (Architecture Decision Record) for this change, in case of architecture or tech stack changes.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes in other branches have been merged
• I have updated the relevant application properties files (if needed)
• I have updated any necessary database migrations (if needed)

Screenshots (for UX changes):

NA

Additional Notes:

NA

[anuragSharma1112]

Hi @axymthr sir, plz review and merge the Pull Request in Develop