HDDS-11199. [Recon] Fix eslint configs and add missing packages for Recon web

[will-sh]

What changes were proposed in this pull request?

HDDS-11199. [Recon] Fix eslint configs and add missing packages for Recon web

Currently, the ESLint configuration in the Recon web project is outdated and missing some essential plugin packages in the devDependencies. This causes the linting process to fail to resolve modern ES6 variables or TypeScript paths properly.

This PR proposes the following improvements to the frontend ESLint configuration:

1. Add eslint-plugin-react, eslint-plugin-import, and eslint-import-resolver-typescript to devDependencies to ensure all required linting plugins are explicitly declared and installed.
   Update .eslintrc.json by adding es6: true to the env block to prevent "undefined" errors for modern JS objects (like Promise, Set, etc.).
2. Configure the import/resolver in .eslintrc.json to correctly resolve .ts and .tsx file paths when using TypeScript in the project.
3. Clean up old/deprecated ESLint rules (such as @typescript-eslint/interface-name-prefix) and adopt the modern recommended import configs (plugin:import/recommended, plugin:import/typescript).
4. Regenerate pnpm-lock.yaml using the official NPM registry to resolve CI test failures related to pnpm install --frozen-lockfile.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-11199

How was this patch tested?

Manually tested in the local environment by running the following commands in hadoop-ozone/recon/src/main/resources/webapps/recon/ozone-recon-web:

pnpm install --frozen-lockfile (Verified successful dependency resolution without any private registry/mirror errors).
pnpm run lint (Verified that ESLint runs successfully without throwing Cannot find module 'eslint-plugin-react' or Unable to resolve path errors).

workflow run on the fork git repo.