QC optimizer doesn't support a custom parameter matrix

Expected Behavior

The QC optimizer should be able to receive a custom 2D matrix of parameters and values such as:

{param_1: [1, 2, 5],
param_2: [10, 15, 35]}

Actual Behavior

The QC optimizer only supports a range of values for each parameter with a static step value, which means that consecutive values in each parameter vector must be equally distant one from another. This poses a problem since a lot of times the sensitive parameter values are found at irregular intervals, and trying every intermediate value in their range increases the optimization cost by a large margin. For example:

# 9 combinations
{param_1: [1, 2, 5],
param_2: [10, 15, 35]}

# vs 30 combinations
{param_1: [1, 2, 3, 4, 5], # step =1
param_2: [10, 15, 20, 25, 30, 35]} # step = 5

Potential Solution

Implementing logic for handling a 2D parameter-value matrix.

Checklist

• I have completely filled out this template
• I have confirmed that this issue exists on the current master branch
• I have confirmed that this is not a duplicate issue by searching issues

Start by locating the QC optimizer entry point and the existing range-based parameter handling. Trace how parameter values and combinations are generated, then identify the tests covering optimizer inputs. Done means accepting the shown irregular value lists and evaluating only their combinations without requiring static steps.