Init Trunk and fix ESLint issues

[gewenyu99]

Hi there, I opened a PR for you to try Trunk Code Quality.

Code Quality will do these things:

• Lint on files changed each commit
• Hermetically install each linter and manage them (so they run the same on every environment and don't pollute dependencies)
• Fixed existing ESLint issues.
• When introducing new linters, they will by default, only run on new issues on the files you change, so this allows progressive enhancement.

Somethings we could do further with Code Quality

• Run in your GitHub actions
• Annotate PRs for files with formatting and linting issues
• Enable Trivy and OSVscanner that require network access, but scans for dependency issues
• Customize ignore and linters.
• Install Trunk VSCode plugin for LSP annotations.

I enabled the following linters, automatically suggested by Code Quality to cover more of your code.

1. General-purpose linters:

   • prettier@3.3.3 (Code formatter for multiple languages)

2. Language-specific linters:

   • eslint@8.57.0 (JavaScript/TypeScript)
   • markdownlint@0.41.0 (Markdown)
   • yamllint@1.35.1 (YAML)

3. Security and vulnerability scanners:

   • checkov@3.2.208 (Infrastructure as Code security)
   • osv-scanner@1.8.2 (Open Source Vulnerability scanner)
   • trivy@0.53.0 (Container and filesystem vulnerability scanner)
   • trufflehog@3.80.1 (Secrets scanner)

4. Docker-specific linter:

   • hadolint@2.12.0 (Dockerfile linter)

5. Git-related tools:

   • git-diff-check (Git diff checker)

6. CI/CD specific linters:

   • actionlint@1.7.1 (GitHub Actions workflow linter)

New commands

• npm lint lint but don't fix
• npm lint:fix lint and prompt to fix
• npm fmt run formatted
• lint-old the old command for reference.

Lmk if you have questions!

[sourabpramanik]

@gewenyu99 Thanks for the PR