Logging present in unit-tests

### Version

main

### Are there any linked Issues or Pull Requests?

_No response_

### What happened?

The infrastructure unit tests are dumping out a lot of log messages at info/warn level, this issue will fix this

### Relevant log output

```shell
14:35:20 Running infrastructure_unit_tests
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
.............................................20260211143539.512+0000:WARN : Mesh C4 already present in collection.
.......20260211143539.639+0000:INFO : Using custom decomposition
...20260211143539.653+0000:INFO : Using custom decomposition
.20260211143539.674+0000:INFO : Using custom decomposition
20260211143539.682+0000:INFO : Using custom decomposition
20260211143539.686+0000:INFO : Using custom decomposition
20260211143539.694+0000:INFO : Using custom decomposition
.....20260211143539.940+0000:INFO : Using custom decomposition
..............20260211143540.452+0000:INFO : Using custom decomposition
.20260211143540.507+0000:INFO : Using custom decomposition
20260211143540.520+0000:INFO : Using custom decomposition
20260211143540.525+0000:INFO : Using custom decomposition
20260211143540.530+0000:INFO : Using custom decomposition
.20260211143540.570+0000:INFO : Using custom decomposition
20260211143540.574+0000:INFO : Using custom decomposition
20260211143540.576+0000:INFO : Using custom decomposition
20260211143540.580+0000:INFO : Using custom decomposition
.20260211143540.723+0000:INFO : Using custom decomposition
20260211143540.723+0000:INFO : Using custom decomposition
20260211143540.734+0000:INFO : Using custom decomposition
20260211143540.736+0000:INFO : Using custom decomposition
.20260211143540.866+0000:INFO : Using custom decomposition
.
20260211143540.881+0000:INFO : Using custom decomposition
20260211143540.891+000020260211143540.892+0000:INFO : Using custom decomposition
:INFO : Using custom decomposition
20260211143540.894+0000:INFO : Using custom decomposition
.20260211143540.910+0000:INFO : Using custom decomposition
.20260211143540.926+0000:INFO : Using custom decomposition
20260211143540.939+0000:INFO : Using custom decomposition
20260211143540.939+0000:INFO : Using custom decomposition
20260211143540.945+0000:INFO : Using custom decomposition
.20260211143540.961+0000:INFO : Using custom decomposition
.20260211143540.988+0000:INFO : Using custom decomposition
20260211143540.998+0000:INFO : Using custom decomposition
20260211143540.998+0000:INFO : Using custom decomposition
20260211143540.999+0000:INFO : Using custom decomposition
.20260211143541.020+0000:INFO : Using custom decomposition
.20260211143541.028+0000:INFO : Using custom decomposition
20260211143541.037+0000:INFO : Using custom decomposition
20260211143541.038+0000:INFO : Using custom decomposition
20260211143541.041+0000:INFO : Using custom decomposition
..........................................................................
....................................................
Time: 25.330 seconds
```

Start by running the infrastructure_unit_tests suite and tracing the INFO and WARN output shown in this issue to its sources. Determine the intended test logging behavior from the surrounding tests and configuration; done means the suite still passes without dumping the reported messages.

Written by the indexing model from the issue text.