Option to disable Suspected Commits

### Problem Statement

Currently, as outlined in [Sentry docs](https://docs.sentry.io/product/issues/suspect-commits/#suspect-commits-without-integrations), the Suspect Commits feature defaults to using a release commit when no other commit information is available (via integrations or manual uploads).

However, relying solely on the release (HEAD) commit is not, in most cases, enough to robustly deduce the causing commit. In our case, a release often consist of dozens of commits and changes to tens of files.

Current behavior can lead to a situation where the developer who last contributed to the release is incorrectly flagged as responsible for the issue. In our case, this can cause more confusion than insight.

### Solution Brainstorm

Add an option to disable the Suspected Commit feature. Optimally, on project level and on organization level.

### Product Area

Issues

Start by reviewing the Suspect Commits behavior described in the linked Sentry docs, then examine how project and organization settings are represented. Define the scope for disabling the feature at each level and document the expected behavior when the option is enabled or disabled.

Written by the indexing model from the issue text.