chore: upgrade @smithy/util-base64

[esauerbo]

Description of changes

Upgrade ^2.0.0 to use 2.2.1, (latest version containing patch)

Issue #, if available

Description of how you validated changes

Checklist

• [ ] Have read the Pull Request Guidelines
• [ ] PR description included
• [ ] Relevant documentation is changed or added (and PR referenced)
• [ ] yarn test passes and tests are updated/added
• [ ] No side effects or sideEffects field updated

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

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 16c69d5481264930bb192cd4992484193cfd4c8f

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

[esauerbo]

Do we need to update the aws sdk packages dep versions for liveness?

I don't think so, because the "@smithy/util-base64@^2.0.0": is what the aws sdk packages reference, and that got updated to 2.2.1 @calebpollman

@aws-amplify/[email protected] -> ./packages/react-liveness
  ├─┬ @aws-sdk/[email protected]
  │ ├─┬ @aws-sdk/[email protected]
  │ │ └── @smithy/[email protected] deduped
  │ ├─┬ @aws-sdk/[email protected]
  │ │ └─┬ @aws-sdk/[email protected]
  │ │   ├─┬ @aws-sdk/[email protected]
  │ │   │ └── @smithy/[email protected] deduped
  │ │   └─┬ @aws-sdk/[email protected]
  │ │     └── @smithy/[email protected] deduped
  │ ├─┬ @smithy/[email protected]
  │ │ └── @smithy/[email protected] deduped
  │ └── @smithy/[email protected]
  └─┬ @smithy/[email protected]
    └── @smithy/[email protected] deduped

[reesscot]

I think for good measure, we might as well update @aws-sdk/client-rekognitionstreaming as well