[Re-Architecture] Migrate the Repo to @nrwl/nx with pnpm support.

[brionmario]

Purpose

Lerna

1. ATM, we are using Lerna as our mono repo management tool in the repo. Lerna has a few issues associated with it when it's used on its own (with the exception of v5 with nx integration support)

• Lerna builds are generally slow due to a lack of support for multiple scheduled tasks at a given time (Pipeline Support).
• No ability to cache prior work.
• Lerna hoist does not support npm ci, which is a security issue.
  • Lerna does not call "npm ci" when hoisting lerna/lerna#2047
• No option to check affected packages to selectively release versions.

npm

Currently, we advise users to use npm as the npm client but the industry has evolved with tools like Yarn and PNPM. For instance, pnpm supports keeping modules in one place and using symlinks to save time and space on consecutive installs.

• npm installs are generally slow.
• npm cache gets corrupted sometimes and can lead to hard troubleshooting issues.
• Less frequent perf and feature updates compared to other alternatives.

Expected Outcome

Nx

1. Improved build performance and cached subsequent builds.

   Performance Gain: 50%

   	Existing Setup	New Setup
   No Cache	15+ mins	7m 51s
   With Cache	15+ mins	1s (If no packages have changed. Only build affected packages)

2. Improved DX with the new nx dev server for react apps that is fast and performant and consume less RAM.

   Performance Gain: 75%

   	Existing Setup	New Setup
   Dev Server Start Time (No Cache)	279.2484s (4.6 mins +)	Less than 1 min

3. Interactive Dependency Graph

pnpm

• With pnpm integration, package installs will be fast and will improve DX.
• With the pnpm upgrade, repos will work with the LTS version of node.

Related Issues

• Address Migrate App Repos to NX & PNPM product-is#13931

Checklist

• e2e cypress tests locally verified.
• Manual test round performed and verified.
• UX/UI review done on final implementation.
• Documentation provided. (Add links if there's any)
• Unit tests provided. (Add links if there's any)
• Integration tests provided. (Add links if there's any)

Related PRs

• None

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Ran FindSecurityBugs plugin and verified report?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?