unify execution pars for dispersive shift

[rodolfocarobene]

Closes #887, but does not take care at all of #890.

How could we use params.execution_parameters and also pass standard values?

Checklist:

• Reviewers confirm new code works as expected.
• Tests are passing.
• Coverage does not decrease.
• Documentation is updated.
• Compatibility with Qibo modules (Please edit this section if the current pull request is not compatible with the following branches).
  • Qibo: master
  • Qibolab: main
  • Qibolab_platforms_qrc: main

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.44%. Comparing base (d209e87) to head (1ba3b8b).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #892   +/-   ##
=======================================
  Coverage   97.44%   97.44%           
=======================================
  Files         115      115           
  Lines        8684     8685    +1     
=======================================
+ Hits         8462     8463    +1     
  Misses        222      222           

Flag	Coverage Δ
unittests	97.44% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
src/qibocal/protocols/dispersive_shift.py	100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes

[alecandido]

Closes #887, but does not take care at all of #890.

That's fine, one issue at a time. #890 is for the longer term

How could we use params.execution_parameters and also pass standard values?

We extend the routine object to contain an ExecutionParameters object, possibly with some fields set to None (that might require a mirror object, to possibly fix the attribute types with Optional), and the executor will inspect the routine attribute when determining which are the params.execution_parameters, setting them according to the following priority:

• explicit routine parameters
• explicit global parameters
• routines default
• global default

and that's what the routine should get access to in the params.execution_parameters. But it has to be implemented at the level of the execution, not the individual routine.

[andrea-pasquale]

Thanks @rodolfocarobene

[andrea-pasquale]

How could we use params.execution_parameters and also pass standard values?

As @alecandido suggested, we can take care of ExecutionParameters in a separate PR.