feat: migrate to biome

[AbhishekA1509]

Description

This pull request migrates the project's linting and formatting setup from ESLint and Prettier to Biome, streamlining configuration and tooling for code quality and consistency. It removes all ESLint and Prettier dependencies and configurations, introduces Biome as the unified tool for linting and formatting, updates scripts and automation to use Biome, and adjusts VSCode recommendations and settings accordingly.

Migration to Biome for Linting and Formatting:

• Added biome.json configuration file to define linting and formatting rules, import organization, and accessibility checks, replacing previous ESLint and Prettier configurations.
• Removed .eslintrc.cjs and .prettierrc.cjs files, eliminating all ESLint and Prettier rules and settings. [1] [2]
• Updated package.json to add @biomejs/biome as a dev dependency, removed all ESLint and Prettier related dependencies, and changed linting scripts to use Biome. [1] [2] [3] [4]

Development Environment Adjustments:

• Changed VSCode extension recommendations to suggest Biome instead of ESLint and Prettier, and updated workspace settings to use Biome as the default formatter and fixer. [1] [2]
• Modified .lintstagedrc to run Biome checks on staged files instead of ESLint.

Script and Codebase Updates:

• Refactored internal scripts (e.g., generate-icon.cjs, generate-illustration.cjs) to use Biome for formatting and linting generated files instead of ESLint. [1] [2] [3] [4]
• Minor cleanup in imports and comments in src/Common/API/CoreAPI.ts to align with new linting practices. [1] [2] [3] [4]

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)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas