Added Eslint and Prettier in the repository

[abhayymishraa]

Description

Added ESLint and Prettier configuration to enforce consistent code style and catch potential issues early in development.

this pr solves - #69

Note :

i have implemented but the checking is not strict so for that if we want to strict check we will need to do many changes i am ready to do the changes
Also i have also implemented prettier-plugin-tailwindcss so that the tailwind clasees would be sorted acc to tailwind

Changes Made

• Added ESLint configuration with React and TypeScript support
• Added Prettier for code formatting
• Configured integration between ESLint and Prettier
• Added necessary dependencies
• Added npm scripts for linting and formatting

##Added new files

• .eslintignore
• .eslintrc.json
• .prettierignore
• .prettierrc

Added Scripts

{
   "lint:check": "eslint --max-warnings 0 --config .eslintrc.json .",
   "lint:fix": "eslint --max-warnings 0 --config .eslintrc.json . --fix",
   "format:fix": "prettier --write \"**/*.{ts,tsx,json}\"",
   "format:check": "prettier --check \"**/*.{ts,tsx,json}\"",
   "vite-plugin-eslint"
}


## Dependencies Added
```json
{
 "devDependencies": {
   "eslint": "^8.57.1",
   "eslint-config-prettier": "^9.1.0",
   "eslint-config-react-app": "^7.0.1",
    "prettier": "^3.3.3",
   "prettier-plugin-tailwindcss": "^0.6.8",
   
 }
}

[yashpandey06]

@abhayymishraa, I think it would be more maintainable if we break these changes into smaller, logically grouped commits. This approach can make it easier for reviewers to follow the changes and verify it .

[abhayymishraa]

@yashpandey06 yes i know but both prettier and lint will be done at the same time mostly if not it will give conflicts and thats why i have disabled all the strict changes we will change when we cnage some part of the code like we should replace any witht the correct format.

[yashpandey06]

Make sense