research: see if there is a better logging solution

### Confirmation

- [x] I have checked for similar issues.

### Problem

We use juju loggo which is really nice however it is expensive to run since it always seems to evaluate the parameters instead of short circuiting the call when in a lower mode.

### Suggested solution

First of all, determine if this is indeed an issue. If it isn't we'll leave it as is.

If it is an issue we have to either replace it or fix it. What we CANNOT lose is the line number and file name, like ```
2025-08-05 13:03:51 INFO tbc tbc.go:1604
```

Start by determining whether juju loggo evaluates logging parameters when the configured level is lower. If it does, compare fixing the existing logger with replacing it, while preserving file names and line numbers in output; the issue names no files or tests to run.

Written by the indexing model from the issue text.