This implements configuration parsing.

• Declare configuration parameters in dist/api_data.py: Add class ConnectionControlPoint and class SessionControlPoint.
• Control point action parsing
  • Sleep: __wt_control_point_config_action_sleep
  • Err: __wt_control_point_config_action_err
  • Ret: __wt_control_point_config_action_ret
  • Wait for trigger: __wt_control_point_config_action_wait_for_trigger
• Control point predicate parsing
  • Skip: __wt_control_point_config_pred_skip
  • Times: __wt_control_point_pred_times
  • Random assigned to WT_CONTROL_POINT.param1.value16aa: __wt_control_point_config_pred_random_param1
  • Random assigned to WT_CONTROL_POINT.param2.value16aa: __wt_control_point_config_pred_random_param2

Note, the control points implementation tickets are in three time periods:

1. POC - Part of the POC.
2. MVP - Part of the minimal viable product. However, even the POC can be used, but less conveniently than the MVP.
3. Future - Enhancements after the MVP.

The title of each ticket starts with the time period.

Status: What is left:

• Write all the config parsing functions above replacing the temporary hard coded values with parsing. It will probably be necessary to add some parameter(s) to the config parsing functions, perhaps the control point name.
• Bug: class ConnectionControlPoint and class SessionControlPoint in dist/api_data.py do not work if name contains a '_' or a space. The bug could be in either dist/api_data.py or dist/api_config.py.