WireMock

What would the full list of scenario state key types be? I'm guessing:

• cookie
• queryParam
• header

I think those 3 would be sufficient. I’d want to see some real-world usage before adding e.g. the ability to select body elements.

It looks like you're planning to allow multiple things in the `scenarioStateKey` - do you expect that to be necessary?

Or just a case of making the API evolvable

I can’t think of any obvious scenarios, but OTOH it’s not that much more complicated to permit &gt;1 key element, but might be a pain to add that later if it turns out to be needed.

I guess there’s a simpler rendering of it e.g.
```"scenarioSessionKey": { "type": "cookie": "name": "JSESSIONID" }```

I wondered if we could start with that, then if someone has a concrete requirement you could add
`"scenarioSessionKeys": []` and the former would become a shorthand for the latter with one key.

Do you think it’s clearer describing it as “session key(s)” specifically or something more generic?

I’m wondering if people will be confused/put off if the thing they’re segmenting on isn’t a session per se.