docs(mac): mention hardened runtime in ad-hoc vs no signing section

[kthchew]

#9007 seems to have caused some confusion because in adding an ad-hoc signature, it caused some projects to unexpectedly have hardened runtime turned on for them. See, for example: #5850 (comment), #9396, #9529

Hardened runtime seems to have been on by default, but this state wasn't applied in the past when no signature was used. See #9529 (comment) for the context.

As a step to try to resolve this, I added a note in the documentation about code signing mentioning this distinction along with the most common issues people may see with this change and their solutions.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0ea37dc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mmaietta]

Merging and bypassing failed test since this is purely a docs update. (The yarn v1 e2e test is flaky due to yarn v1 resolution logic, but other versions seem to test stable)