chore: migrate to Tailwind CSS v3 and update config

[lightning-sagar]

Description

Changes proposed in this pull request:

• upgraded styling dependencies:
  • [email protected]
  • postcss@8
  • autoprefixer@10
  • @tailwindcss/[email protected]
• replaced deprecated purge option with the new content field in tailwind.config.js
• removed unused darkMode configuration (darkMode: false)
• removed default fontSize values only those are already provided by tailwind v3
• updated borderColor signature from theme => ({}) to ({ theme }) => ({})
• updated plugin function from borderColor to typography
  these changes are done for the Library Dir, and the rest are already using tailwind-v3.

Related issue(s)

Resolves #1150

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[lightning-sagar]

maintainers, please let me know if you would prefer migrating directly to tailwindcsss v4.

since the issue mentions upgrading to v3, I have completed the migration accordingly. but, tailwind v4 has been released, so if the project intends to move to the latest version instead, I can update the migration work to v4 in a follow up pr or adjust this one as needed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud