Various comment reply fixes (muting/reporting)

[DejayJD]

Description

Started with a simple task and ended up tackling a ton of stuff

• [C-5195] Delete comment making count go up
• [C-5188] Fixed all issues with mutes not affecting replies (both backend & query)
• [C-5187] Fixed all issues with reports not affecting replies (both backend & query)
• [C-5169] Flag & hide still showing "hide replies"
  Other fixes
• Updated reply load logic to always use reply_count; fixes bugs where "Show more replies" was showing when it didn't need to
• Fixed race condition with currentUserId where comments data could get loaded with an undefined user id (and get cached)
• Fixed delete reply not affecting reply count
• Added a loading spinner to the "Show more replies" button while loading a page (also disabled the button)

How Has This Been Tested?

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: e7b17df

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/jd/mute-and-report-fixes

[sliptype]

good stuff!

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11648680	Triggered	Generic High Entropy Secret	b9c4781	dev-tools/templates/test-localhost.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[audius-infra]

Preview this change https://demo.audius.co/jd/mute-and-report-fixes