chore: Update dependencies for Composer and extensions

[BruceHaley]

Fixes #minor

Changes

1. Update yarn from 3.1.1 to 3.2.1. Needed for #⁠2. See .cjs files
2. Add up-all plugin. Allows updating dependencies with exclusions. Needed for #⁠3. See yarn-up-all-plugin.cjs
3. Add "Update Composer dependencies" github workflow. Extensions dependencies updating is complex enough that automation is left for a later PR.
4. Update dependencies for Composer and for extensions. See package.json and yarn-berry.lock files.
5. Fix eslint lodash/path-style errors. Change these errors to warnings. See Composer/.eslintrc.js.
6. Fix eslint security/detect-unsafe-regex errors. Disable this rule at specific lines. See .ts files.
7. Tweak azure-pipelines.yml for readability.

[coveralls]

Coverage remained the same at 54.547% when pulling 07ac795 on bruce/yarnuptest7-6e into d1789e4 on main.

[tonyanziano]

Looks good to me, going to wait for E2E to run and then locally test the windows and linux builds to make sure there are no obvious issues.

[tonyanziano]

awesome!

[tonyanziano]

Looks like all the tests are passing, it's only failing on the security alerts which will eventually be fixed as a result of this PR. Going to check the production apps built from your branch.

[tonyanziano]

Tested the mock build on all 3 platforms. Looks good!