Upgrade project to Yarn 4 (Corepack)

[satnam72]

Description:
The project currently builds inconsistently across environments due to Yarn version mismatches. Some workflows, Docker images, and local setups still use Yarn 1.x or 2.x, while the project package.json now specifies Yarn 4.x via Corepack.

Goals:

1. Ensure all workspaces and Docker builds use Yarn 4.x consistently.
2. Enable Corepack in Dockerfiles and CI workflows.
3. Regenerate yarn.lock files for all workspaces using Yarn 4.
4. Update documentation for local development and CI/CD to reflect Yarn 4.

Benefits:

• Consistent dependency resolution across all environments.
• Fixes CI/CD build errors caused by Yarn version mismatch.
• Prepares project for better future dependency management using Yarn 4 features.

Next Steps:

• Audit all workspaces and Dockerfiles for Yarn version usage.
• Enable Corepack and lock Yarn 4 version globally in workflows.
• Test builds locally and in CI/CD after migration.

[Harshalyadav]

Thanks for the detailed proposal, @satnam72. This migration to Yarn 4 via Corepack looks necessary and well-scoped.

I’d be happy to help with this—could you please assign this task to me? I can start by auditing the workspaces and Dockerfiles and proceed with the Corepack and lockfile updates.