Make WorkBench and Batch Edit transfer checks context aware

[acwhite211]

Fixes #7810

Change Owner could be hidden even when a user had the correct dataset transfer permission, because the UI also depended on unrelated SpecifyUser read access.

This change makes dataset ownership transfer context aware and scoped to the active dataset type. WorkBench datasets use /workbench/dataset transfer permission. Batch Edit datasets use /batch_edit/dataset transfer permission. Transfer recipients are loaded from a dataset scoped endpoint instead of querying SpecifyUser directly from the front-end.

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list
• Add automated tests
• Add a reverse migration if a migration is present in the PR

Testing instructions

• Keep the RBGE Researcher role assigned to the test user so the dataset can be opened.
• Assign WB Transfer (No BE) to the test user.
• Confirm the user has WorkBench > Transfer and does not have Batch Edit > Transfer.
• Log in as that user.
• Open a standard WorkBench dataset (not a Batch Edit dataset).
• Click Tools.
• Verify the Change Owner button is visible.
• Click Change Owner and verify the dialog opens and the recipient list loads.
• Close the dialog without making changes.
• With the same roles still assigned, open a Batch Edit dataset.
• Click Tools.
• Verify Change Owner is not shown for Batch Edit when Batch Edit > Transfer is missing.
• Add the role WB Transfer (or otherwise grant Batch Edit > Transfer) to the same user.
• Reopen the Batch Edit dataset and click Tools.
• Verify Change Owner is now shown for Batch Edit as well.