chore(storage-browser): add react-router app, add StorageBrowser examples, add @aws-amplify/ui-test-utils

[calebpollman]

Description of changes

• add "@aws-amplify/ui-react-router-example" app

  • add defaultValue, legacy controlled (location, actionType and path props), and improved controlled value examples
  • add configurable react-scan perf util

• update "@aws-amplify/ui-next-app-router-example" app

  • update name field of package,json: "@aws-amplify/ui-app-router-example" -> "@aws-amplify/ui-next-app-router-example"
  • add legacy controlled (location, actionType and path props) and improved controlled value examples
  • update react-icons dep due to failing imports

• update "@aws-amplify/ui-next-pages-router-example" app

  • update name field of package,json: "@aws-amplify/ui-next-example" -> "@aws-amplify/ui-next-pages-router-example"
  • update react-icons dep due to failing imports

• add @aws-amplify/ui-test-utils internal package

  • add StorageBrowser mock handlers/state
  • add eslint, typescript and rollup configs

Issue #, if available

NA

Description of how you validated changes

Manual testing

Checklist

• Have read the Pull Request Guidelines
• PR description included
• yarn test passes and tests are updated/added
• PR title and commit messages follow conventional commit syntax

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 41d9ff5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[AllanZhengYP]

Looks good to me!

[AllanZhengYP]

Nit, put explanations after expect-error.

[AllanZhengYP]

Is this intentionally comitted?

[calebpollman]

Goes question! Yes, it indicates what .env should look like for enabling react-scan