Every time you launch MuseScore, macOS Sonoma asks about allowing MuseScore to access data from other apps; caused by MuseSampler

Every time you launch MuseScore on macOS Sonoma, the system asks about "allowing MuseScore to access data from other apps". The dialog looks like this: (I only have the Dutch version at hand, sorry)

Apparently, more people are experiencing this: https://musescore.org/en/node/356030

My current hypothesis about why this happens is the following:
Context: On macOS, apps can be sandboxed. Sandboxed apps cannot read/write files on the user's disk directly; instead, they can only interact with a special folder called ~/Library/Containers. These apps won't notice that though; they just try to interact with normal paths, and macOS routes that to subfolders of ~/Library/Containers. If an app wants to access the user's Desktop folder, then macOS shows a popup asking for permission; if the user allows it, an alias to the Desktop folder is created in ~/Library/Containers, so that the app can read it. If the user disallows, the app cannot see the Desktop folder.
FWIW, MuseScore is not sandboxed, so the rules about permissions work a bit differently, but Muse Hub is sandboxed.
Anyway, this new macOS Sonoma warning means that MuseScore is trying to read data from another app's sandbox. Which app? The answer turns out to be Muse Hub. Muse Hub downloads all Muse Sounds data to its sandbox folder, and MuseScore reads it from there, albeit via the MuseSampler library (but macOS considers that library as a part of MuseScore if it has been loaded by MuseScore).
Evidence: this is a snapshot of MuseScore's main thread at the moment that macOS shows the permission dialog:

Solution: Muse Hub should put sounds in a different location.
(Also, Muse Hub's container is not the best place for sounds anyway, since containers are user-specific instead of system wide. So if multiple users on one Mac use Muse Sounds, each user will need to install a separate copy of the sounds.)