[QA-1357] Remove excessive polling and amplitude events in unlock

[raymondjacobson]

Description

Removes listening for cache updates in the gated content unlock flow. This fixes an issue where every time the polling function runs, it issues a cache update, which triggers another poller to run (firing about 100 amplitude events when unlocking a single track).

The original change was made here: https://github.com/AudiusProject/audius-client/pull/2642/files#diff-c0963e4a508d816d128ccb03764a0ccd0b61a04092b2c672f89ee778dfb15130L336
I don't understand the original intent - as in - I'm not sure when an update would need to trigger polling for content access, but @sddioulde you may know?

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide repro instructions & any configuration.

Unlocked a follow-gated track on stage

Also completed a purchase and an nft unlock for sanity

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4b5b088

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

[audius-infra]

Preview this change https://demo.audius.co/rj-qa-1357

[raymondjacobson]

Merging this with the caveat that @sddioulde and i synced and can't really figure out what edge case the original code was trying to prevent. Probably deserves another look and some more thorough testing.