Ability to add "jvm arguments" based on "@Param"

[Vladimir Sitnikov]

I see two main use cases:
1) Generate unique set of logs per iteration.
For instance:
1,1) being able to use unique names for -Xloggc, -XX:+FlightRecorder options
1.2) use different jar files in the classpath (in case of non-shaded dependency)
1.3) being able to calculate OperationsPerInvocation.

2) Explore search space. For instance, if parameters are dependent, it
could make sense to investigate different combinations.

In case #1, additional configuration of OptionsBuilder is performed
_after_ jmh picks the values for all the parameters.
We can have even some kind of predefined "post-processors": "save gc
logs to gc_param1value1_param2value2.log like files".

In case #2 some kind of Supplier is required.


It looks case #1 happens more often, and it is somewhat different from
#2, so they can be treated differently.

Any thoughts on that?

Vladimir