On macOS Picard is using the system wide libdiscid if available, and only uses the app bundled one if there is no system wide.

In the specific case libdiscid was also installed in /usr/local. When loading python-discid it tries to load from system wide location, even if this fails. It will only attempt to load the bundled libdiscid if there is no system wide libdiscid.

This causes problems if:

1. The system wide libdiscid is an older version, resulting in bugs or missing functionality
2. The system wide libdiscid cannot be loaded, resulting in discid lookup being disabled

Case 2 is especiall problematic when enabling the "Hardened Runtime" (PICARD-1653), as this will prevent loading libdiscid.dylib until it has been signed. An unsigned system wide install of libdiscid is unsable.