[#1904] Add ESLint support for TypeScript imports

[vvidday]

Fixes #1904

Proposed commit message

ESLint is currently not configured to properly support TypeScript
imports. This results in an error when importing local TypeScript files
with the file extension omitted, which is the default way to import
TypeScript files.

Let's configure ESLint to support TypeScript imports and enforce the
omission of file extensions for .ts and .js files. This will allow us to
pass the lint check while using the default import method, and enforce
consistency throughout the codebase.

Other information

Changes to .eslintrc.json

Adding plugin:import/typescript allows ESLint to properly resolve TypeScript imports that don't include the .ts file extension, which solves the "Unable to resolve path to module '../..'" error.

   "import/extensions": [
      "error",
      {
        "js": "never",
        "ts": "never"
      }
    ]

The above lines configure the import/extensions rule to make sure imports should never end with .js or .ts. If the rule is broken, it will be considered an error by ESLint. This solves the "Missing file extension for '../..'" error.

Others

The other changes are removing the .ts extensions from existing imports.

[ckcherry23]

LGTM!

[zhoukerrr]

LGTM!

[github-actions]

The following links are for previewing this pull request:

• Dashboard Preview: https://dashboard-1905-pr-reposense-reposense.surge.sh
• Docs Preview: https://docs-1905-pr-reposense-reposense.surge.sh