megatask: Audit and unify logging throughout collectoss

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

---

While tracking down https://github.com/chaoss/augur/issues/3306, I noticed that the logs (in facade) are both:
1. using a custom logging wrapper function
2. being written to a database table

while an unconventional practice, writing to the database can be done using existing output features of the logging package in python, allowing logging in facade to use standard calls like `logger.warn(message)` rather than custom functions like this.

Also there are many places throughout the code that are using print() statements rather than the python logging library

This suggests we should probably audit all the logging calls in augur to see if we can simplify everything under one system (and also potentially ask why we need logs in the database).