I'm pretty sure the answer is No, and I think that's true for all of the major tools. (GitHub, Azure DevOps, GitLab, Bitbucket, etc.)
Perhaps the two main reasons this functionality doesn't exist are both things you mentioned:
these use-cases aren't as common as I'd imagined
Force pushing shared branches should be a rare event.
The use-cases for this would be for instance to clean up the git history (without any actual code changes)...
Most code review tools are file-centric, and as you mentioned, even if there was a mechanism for code reviewing a reset, there actually wouldn't be any files to review. You'll still need to inspect the commits, but as mentioned below you can just do it manually on the machine that contains the new code.
As for your sub-question:
I'm looking for standard ways that these things get done.
I don't know of any (popular) standard for resetting shared branches, perhaps because it's odd to create a standard around something that is frowned upon and should be rare. That being said:
My preferred method for resetting a shared branch goes something like this:
Decide if you really need to reset, or if a revert will suffice. (Usually the suggestion to reset is due to regretting merging in some code, and in that case a revert can undo it too. In your case, revert doesn't apply since your desire is to clean-up history. You'll have to reset, so you can skip this step, or, perhaps you need to decide if you really need to reset it.) If you decide not to reset, you're done here. (Reverts use the normal code review process.)
Consider locking down the shared branch so no one adds more to it while you're re-writing it.
Determine the best commit to reset to. For undoing regrettable merges, normally you reset backwards to a commit already in the history, perhaps just before the problem, but if you're rewriting history it's likely it won't be in the history at all. In the case of a rewrite you'll likely need to review your code outside of the normal review process. Typically, on someone's machine that contains the rewritten code, you compare the end states and make sure the only differences are whatever you wanted to strip out. Then you spot check specific commits to make sure the large files, passwords, etc, no longer exist anywhere in the history.
If you haven't already, announce to your entire team that a shared branch is going to be re-written and provide instructions for how to rewrite their WIP branches. Make sure to include the previous tip commit ID of the branch getting rewritten, as well as the proper command(s) to run. Perhaps something like:
git fetch
# for each feature branch in progress:
git rebase <old-tip-commit> my-feature-branch --onto <shared-branch-name>
If you use protected branches, temporarily give someone (perhaps the person who has the rewritten history on their machine) permission to force push the shared branch.
Force push the shared branch with the safety net, particularly if you didn't lock it as suggested above:
git push --force-with-lease
Remove the temporary permission to force push the shared branch.
Announce to your team that it's done and that they can now rewrite all of their WIP branches.
