Allow "Enhanced Privacy" configuration to be overridden per-project

### Problem Statement

This is a dupe of #2786 which is locked and I cannot comment., but I also encountered this and would like it.

> In our organization, one of the main systems (i.e. projects) has sensitive information, so we've enabled "Enhanced Privacy" org-wide to ensure that we don't leak stacktraces email for that particular system. But the majority of our projects aren't sensitive, and there's high utility in having stacktraces delivered to email for those systems.
>
> "Enhanced Privacy" only seems configurable at the org-level; is there any reason we shouldn't offer the ability to override that configuration per project?

### Solution Brainstorm

_No response_

### Product Area

Unknown

No files or tests are named. Start by reviewing the existing organization-level Enhanced Privacy configuration and the locked duplicate issue #2786, then trace how project settings are loaded and enforced. Done means a project can override the organization setting without weakening the organization default, with coverage for both configurations.

Written by the indexing model from the issue text.