✨ Improving documentation to make it more explicit which benchmarks trigger an optimization procedure when generated

[nquetschlich]

What's the problem this feature will solve?

Some of the benchmarks (e.g., VQE, QAOA, Portfolio benchmarks, etc.) have parameterized gates. To determine their values, a short optimization procedure is triggered which still takes some time.

Describe the solution you'd like

The documentation should highlight which benchmarks are affected by this. Alternatively, one could think about assigning random parameter values since the optimized ones are most likely also far from optimal.