Dont use hardcoded version numbers in DB inserts

> [!NOTE]
> Migrated from [augurlabs/augur#3486](https://github.com/augurlabs/augur/issues/3486)
> Originally opened by `@MoralCode` on 2025-12-19

---

There are many places where augur writes a hardcoded version number to the database:

https://github.com/chaoss/augur/blob/a60ddeaada89a5708e162600bec884e635f1de0e/augur/tasks/git/dependency_tasks/core.py#L129
https://github.com/chaoss/augur/blob/a60ddeaada89a5708e162600bec884e635f1de0e/augur/tasks/git/dependency_libyear_tasks/core.py#L55
https://github.com/chaoss/augur/blob/a60ddeaada89a5708e162600bec884e635f1de0e/augur/tasks/git/util/facade_worker/facade_worker/analyzecommit.py#L191
https://github.com/chaoss/augur/blob/a60ddeaada89a5708e162600bec884e635f1de0e/augur/tasks/github/pull_requests/commits_model/core.py#L68
https://github.com/chaoss/augur/blob/a60ddeaada89a5708e162600bec884e635f1de0e/augur/tasks/github/repo_info/core.py#L226

... and many more.

some of these are clearly out of date. Others are so old that I suspect they may be referring to versions other than the augur core version.

For this issue: any of these that are supposed to refer to augur version numbers should import/read this value from `metadata.py` (and maybe it should move into the augur source tree)