Align fork metrics with CHAOSS Technical Fork definition

[HimasreeKolathur24]

Description

• This PR aligns Augur’s existing fork metrics (forks and fork_count) with the CHAOSS Technical Fork canonical definition by updating their documentation. The metrics now explicitly describe platform-native technical forks as defined by CHAOSS, without changing any existing logic or database schema.

This PR fixes #2603

Notes for Reviewers

• No functional changes were made; this PR only updates metric documentation to align with the CHAOSS canonical definition.
• No database or API behavior changes are introduced.

Signed commits

• Yes, I signed my commits.

[MoralCode]

Im a little unsure how these new docs relate to the actual functionality, if we are changing the docs, I want to make sure they align with the actual implementation. If those endpoints dont actually represent the technical fork metric, that would need fixing before this merges.

Do you have any evidence that these endpoints truly do implement this metric? Can any other maintainers vouch for this?

[shlokgilda]

Yeah, these endpoints do implement the CHAOSS Technical Fork metric correctly.

I think this is the data flow. Didn't really dove deep into it though:

1. GitHub GraphQL API forkCount → collected here
2. Stored in repo_info.fork_count → line 203
3. These metrics query that column

GitHub's forkCount only tracks server-side forks. This matches the CHAOSS definition - platform-native forks excluding local clones.

@HimasreeKolathur24 Left some line comments on formatting issues (docstring indentation).

[HimasreeKolathur24]

@MoralCode, @shlokgilda,
Thanks for the review and suggestions! I’ve fixed the docstring indentation for both forks and fork_count, squashed the commits into a single clean commit, and addressed the formatting feedback. No functional changes were made.