[WIP] Refactor state variables to handle inputs

[EZoni]

Overview

• Merge all previous data structures used to handle input values and information into a single dictionary, expanded from the dictionary parsed from the experiment configuration file by adding the keys "value", "step", and "show_all". For example,

  {'input1': {'name': 'Preplasma Z (MFA)',
    'type': 'scalar',
    'default': 12.1,
    'value_range': [11.85, 12.15],
    'value': 12.1,
    'step': 12.031500000000001,
    'show_all': False},
   'input2': {'name': 'DAZZLER-LT-3rdorder value1',
    'type': 'scalar',
    'default': 80000.0,
    'value_range': [-80000.0, 80000.0],
    'value': 80000.0,
    'step': 80800.0,
    'show_all': False}}
  

  This data structure mimics closely what is found in the experiment configuration file and it could allow even further expansion, such as the one suggested in [WIP] Add control to select type of inputs displayed #356 (comment), in a straightforward way.
• Use uniform naming conventions for inputs and outputs between experiment configuration files and the dashboard code base. In particular, use inputs for input variables, outputs for output variables, and drop synonyms such as parameters, input_variables, output_variables, objective_name, etc.

To do

• Drop objective_name.
• Fix calibration manager.
• Fix optimization manager.
• Rename state.inputs_new as state.inputs