Fixed linting for local development

[mokshith-moksh]

Linked Issue(s)

Closes #600

Acceptance Criteria fulfillment

• The linter should work locally on respective submodules.
• The linter should run on saving of files (only the currently changed file(s) ideally).
• It should work on respective files regardless of whether I opened the submodule directly or the whole repo.
• It should work at least in VSCode perfectly.

Proposed changes

Further comments

The solution involved configuring the ESLint settings in both the CLI and web-server submodules to ensure consistent behavior across the repository. I prioritized getting it to work seamlessly in VSCode, as specified in the acceptance criteria. Alternative approaches were considered, but this configuration best meets the project's linting requirements.