New macOS Universal Binaries are signed

Our new Unversal Binary Executable is now signed, while our old executables where not signed at all. This might create different behaviour related to security prompts.

We might need to discuss whether we should just remove the signature (if possible), or whether we need to sign it in a proper way.

Old Executable:
```
# codesign -dv --verbose=4 solc-macos
solc-macos: code object is not signed at all
```

New Universal Binary Executable:
```
# codesign -dv --verbose=4 solc-macos
Executable=solc-macos
Identifier=main-arm64.out
Format=Mach-O universal (x86_64 arm64)
CodeDirectory v=20400 size=298023 flags=0x20002(adhoc,linker-signed) hashes=9310+0 location=embedded
VersionPlatform=1
VersionMin=853248
VersionSDK=917504
Hash type=sha256 size=32
CandidateCDHash sha256=d5ab423e4c721c7d8cb5069e0460765e0f1ffdb5
CandidateCDHashFull sha256=d5ab423e4c721c7d8cb5069e0460765e0f1ffdb5a3f6da425901ff6b1291e7c4
Hash choices=sha256
CMSDigest=d5ab423e4c721c7d8cb5069e0460765e0f1ffdb5a3f6da425901ff6b1291e7c4
CMSDigestType=2
Executable Segment base=0
Executable Segment limit=24353728
Executable Segment flags=0x1
Page size=4096
CDHash=d5ab423e4c721c7d8cb5069e0460765e0f1ffdb5
Signature=adhoc
Info.plist=not bound
TeamIdentifier=not set
Sealed Resources=none
Internal requirements=none
```

Start with the old and new solc-macos artifacts and reproduce the two codesign -dv --verbose=4 outputs on macOS. Determine whether the ad hoc linker signature changes security prompts and whether the intended outcome is removing it or signing properly. Done means an agreed signing policy and matching release artifact behavior.

Written by the indexing model from the issue text.