chore(storage-browser): Update control unit tests to be more isolated

[cshfang]

Description of changes

This PR streamlines the control unit tests to isolate its mocks a bit better so that it is not implicitly testing upstream dependent components

Issue #, if available

Description of how you validated changes

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
• If this change should result in a version bump, changeset added (This can be done after creating the PR.) This does not apply to changes made to docs, e2e, examples, or other private packages.

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: 5da2670

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

[jordanvn]

These changes mstm. Confirmed no regressions locally, and for this improves overall coverage as well.

[pranavosu]

we could consider using mock onRefresh from line 19, possibly expect onRefresh: mockOnRefresh instead of any function. this applies to a lot of the other tests, but i don't think it's critical.

[cshfang]

Yeah, I had considered doing this but we'd have to pull them out into const mockOnRefresh = jest.fn() just to assert something that's more or less trivial in the end. So just opted to keep it marginally more concise