We have our own signing mechanism, and they conflict making the Apple signature invalid

Until a few days ago, for nightly or releases extensions, we built the binary, codesigned, then applied our signature on top (making the Apple signature not valid anymore).
With the extension metadata rework, we applied our own signature as part of cmake, and this breaks the preconditions of Apple codesigning.
Even if that would be solved, we still modify the binary afterwards.

And another connected problem: codesigning was performed only for extensions built directly by duckdb/duckdb workflows, and not for out-out-tree ones (then possibly updated to extensions.duckdb.org).

All consider, I think the proper solution is just removing the codesigning step on extensions. To be reviewed whether it makes sense and can be introduced everywhere.