fix: upgrade most packages that use rimraf and glob

[ShadowCat567]

Description of changes

Currently when you install @amplify/cli, this message appears:

npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported

This PR is an attempt to upgrade as many packages as possible that use the deprecated version of these dependencies as well as upgrade the versions of rimraf and glob that are used in our repository (inflight is a dependency of versions of glob before v9, upgrading to v9 or higher resolves the inflight problem).
Many packages were out of date and using deprecated versions of rimraf and glob that had memory leaks. This PR fixes the vast majority of the outdated packages.
Some notes about glob and rimraf:

• glob and rimraf not longer have default exports, since we were using rimraf.sync and glob.sync, I switched us to their named export equivalents
• apparently -f/-r/-rf has never done anything, it seems people would add them because rm takes these arguments

Moved some of the packages that cannot be updated to devDependencies.
Most remaining outdated packages that have not been moved to devDependencies come from data repositories, these will be addressed in a separate PR.

Issue #, if available #13889

Description of how you validated changes

Ensured that the project still builds and the tests still work.

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]

Do we need this PR?

[ShadowCat567]

Do we need this PR?

This is an attempt to upgrade packages that use old versions of glob and rimraf, since when you install amplify-cli this message appears:

npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported

The memory leak issue is the most concerning of the 3 warnings, and it comes from versions of glob prior to v9 having a dependency on inflight (older versions of rimraf have a dependency on glob, so they also have this memory leak issue).
This PR aims to get as many packages as possible to use recent version of rimraf and glob, however it is not possible to get all of our packages in Gen1 CLI to stop using old version of rimraf and glob since we have some deprecated packages (like istanbul) that use them and won't receive updates.
If you think that because we can't entirely upgrade out of using old version of rimraf and glob, this PR is irrelevant, I can close it.

[ShadowCat567]

Do we need this PR?

Additionally if this PR is deemed unnecessary, is it worth the effort to do similar updates in the Gen2 CLI and Data repositories?

[Amplifiyer]

We should do this unless there are blockers. Also looking at istanbul it seems we are not even using it anymore? I don't see the coverage:collect being used anywhere. If we can remove it even better.

[Amplifiyer]

Looks good overall.