fix: yarn modern install workspace

[0618]

Description of changes

Issue: Modern Yarn (2,3) doesn't create yarn.lock when running yarn install if it can find a yarn.lock in it's parent directory. So we can see the folloing error:

#13001

Fix: Add yarn.lock to category resources directories if there's no yarn.lock

Issue #, if available

Description of how you validated changes

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)
• New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
• Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[Amplifiyer]

Can't we use this new https://yarnpkg.com/configuration/yarnrc#nmHoistingLimits i.e. creating .yarnrc.yml for yarn3 workspaces instead?

Also we should have automated tests for this change.

[0618]

Can't we use this new https://yarnpkg.com/configuration/yarnrc#nmHoistingLimits i.e. creating .yarnrc.yml for yarn3 workspaces instead?

Also we should have automated tests for this change.

That's a good point. Thanks for pointing it out.

However, it only works if we modify the .yarnrc.yml in the root directory. It doesn't work if we add .yarnrc.yml in the resource' directory

However, it work either of the following case:

1. modify/add .yarnrc.yml in the root directory. OR,
2. add both .yarnrc.yml and yarn.lock in the resource directory, which means it additionally modify the .yarnrc.yml on top of the current PR

Option 1 is not good because I don't think we want to modify anything outside the amplify/ directory.
Option 2 is not necessary because adding yarn.lock alone is enough for us.

[sobolk]

We should add tests.

[0618]

failed e2e tests are: l_diagnose_hooks_a_mock_api and l_function_3a_init_special_case_http_migration, which are the same as the dev branch. They are not from this PR.