chore(ui-dev): migrate `tslint` to `eslint` (#11652)

[Marvin9]

fixes #11652

This PR

• removes deprecated ui linter tslint
• introduces eslint with standard config related to typescript and react
• integrate prettier in eslint itself using eslint-plugin-prettier
• replaces tslint related commands with eslint
• bumps prettier version from 1 to 3
• adds documentation for smooth development workflow in VSCode.
• Includes the automatic lint fixes by yarn lint:fix (which uses eslint command)
• Includes manual lint fixes and for safe side, instead of fix, I added eslint ignore comment for those particular lines.

Checklist:

• [x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• [x] The title of the PR states what changed and the related issues number (used for the release note).
• [ ] The title of the PR conforms to the Toolchain Guide
• [x] I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• [ ] I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• [x] Does this PR require documentation updates?
• [x] I've updated documentation as required by this PR.
• [x] I have signed off all my commits as required by DCO
• [ ] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• [ ] My build is green (troubleshooting builds).
• [ ] My new feature complies with the feature status guidelines.
• [x] I have added a brief description of why this PR is necessary and/or what this PR solves.
• [ ] Optional. My organization is added to USERS.md.
• [ ] Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[crenshaw-dev]

This is awesome. I notice a huge part of the diff is just trailing commas. Would it be possible to remove that lint rule to make the diff more readable? We can always have a follow-up PR to make that change.

I didn't read too far, but I'd recommend taking that route for any rules which have changed a lot of lines.

[Marvin9]

Sorry forgot to explain the reason for the commas (why wasn't there before).

When I bumped the prettier version from 1 -> 3, the default configuration was probably changed. Thus with this new version, we need to explicitly state that we don't want trailing commas.

[crenshaw-dev]

Makes sense! I'm also up to change that config if people want, just better to be in a standalone PR.