Add Clones metric API (#2604)

[saksham23467]

Description
This PR implements the Clones metric API as defined by CHAOSS. It returns the number of repository clones (both total and unique) for a given repository or repo group, filtered by an optional time range.

Fixes
Fixes #2604

Notes for Reviewers

• The metric fetches data from the augur_data.repo_clones_data table.
• It supports filtering via repo_id, repo_group_id, begin_date, and end_date.
• The logic is consistent with other metric implementations in the codebase.
• Please verify the SQL query structure and parameter usage.

Signed commits

• Yes, I signed my commits.

[saksham23467]

Hi! This is my first contribution to CHAOSS. Please let me know if any changes are required. Looking forward to your feedback!

[Ulincsys]

There are extra changes in this PR that should not be included.

Please rebase and remove the extra changes from each PR, and I can review them independently.

[Ulincsys]

Your error handling changes were included in this PR, and also #3248

[saksham23467]

Sure, i’ll make the changes in a while , i am having my exams right now.

…

On Mon, Sep 15, 2025 at 9:27 AM John McGinness ***@***.***> wrote: ***@***.**** requested changes on this pull request. There are extra changes in this PR that should not be included. Please rebase and remove the extra changes from each PR, and I can review them independently. — Reply to this email directly, view it on GitHub <#3247 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCCKHZZBKAL257YKR6AR4Z33SY2LRAVCNFSM6AAAAACCZY7X2KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTEMRSHAZTSMRYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[sgoggins]

This has been sitting here for a while and we are going through things ... it does not look like its been tested, and its pretty isolated from our other code ... AND, these metrics are NOT USEFUL UNLESS YOU ARE USING AN API KEY that has maintainer rights on the repos you are getting data for. So, if you are running Augur only on the repos you have those privileges on you will get this data ... most OSPO driven Augur instances will not be able to capture this data.