Add support for CODEOWNERS for forked repositories

### Problem Statement

Currently, if you have a forked repository that has fewer stars than the parent repository, you are unable to import a CODEOWNERS file. Sentry cannot find the CODEOWNERs file.

This is because Sentry uses the [code search API](), which says:

> Code in forks is only searchable if the fork has more stars than the parent repository. Forks with fewer stars than the parent repository are not indexed for code search. To include forks with more stars than their parent in the search results, you will need to add fork:true or fork:only to your query. For more information, see "Searching in forks."

As a result of this, when Sentry tries to locate the CODEOWNERS file, it cannot if the forked repository contains fewer stars than the parent.

### Solution Brainstorm

If Sentry is unable to find a CODEOWNERS file, allow the user the enter the file path manually and check that Sentry can access it from the backend.

Alternatively, just look for the CODEOWNERS file in the accepted locations (root, .github, .docs).

### Call to action

Would this feature have helped you? If yes, please like this issue so that we can prioritize it.

We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples**:**

* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs

---

**Candidate Metrics (add more below)**

* …

*(please also add ideas, questions or examples in comments)*