Add small parameter representation guide for the benchmark runner

We recently changed the way parameters are injected into the benchmark records. All Python-native types and containers thereof are passing unchanged, but user-defined types are serialized to string (their repr() outputs to be exact), which can be surprising.

Since we do not yet mention this anywhere in the docs, we could set up a small section on this practice, and recommend a way to handle types for best odds of reproducibility (e.g. dumping unique information into the output, or overloading the repr() method to give all unique info).

Look at the benchmark runner code that injects parameters into records, likely in a file like runner.py or record.py. Examine how parameters are serialized, focusing on the handling of user-defined types. Review existing documentation to find where to add a new section explaining the repr() serialization practice and recommendations for ensuring reproducibility.

Vom Indexierungsmodell aus dem Issue-Text verfasst.