Windsock: redis benches - generate topology.yaml

[rukai]

blocked on:
#1334
#1335
#1336

This PR begins a refactor for windsock to define its topology.yaml files using the config structs from shotover and serializing them to yaml.
This allows us to programmatically create the configuration we need for windsock.
The advantages of this are:

• avoids an exponential blow up in unique topology.yaml files. I wanted to add more cases to windsock but found I would have to double the number of unque topology.yaml files for kafka from 4 to 8.
• Allows us to reuse more logic between local and cloud runs, particularly important because we currently do not run cloud benches in CI.

However this comes at the cost of introducing a lot of complexity where previously it was simple but just repetitive.

I currently think that we should never use this topology.yaml generation for our integration tests because having hardcoded yaml files is easier to understand, and allows us to properly integration test shotover as average users will have to write these files by hand.