Add tutorial for device overrides feature

Explanation of changes

Tutorial for the device_overrides feature.

---

Merge checklist

See also merge request guidelines

• Merge request has been reviewed (in-depth by a knowledgeable contributor), and is approved by a project maintainer.
• New code is covered by unit tests (or N/A).
• New code is documented and docstrings use numpydoc format (or N/A).
• New functionality: considered making private instead of extending public API (or N/A).
• Public API changed: added @deprecated and entry in deprecated code suggestions (or N/A).
• Newly added/adjusted documentation and docstrings render properly (or N/A).
• Pipeline fix or dependency update: post in #software-for-developers channel to merge main back in or update local packages (or N/A).
• Tested on hardware (or N/A).
• CHANGELOG.md for breaking changes and AUTHORS.md have been updated (or N/A).
• Update Hardware backends documentation if backend interface change or N/A
• Check whether performance is significantly affected by looking at the Performance metrics results.
• Windows tests in CI pipeline pass (manually triggered by maintainers before merging).
  • Maintainers do not hit Auto-merge, we need to actively check as manual tests do not block pipeline

---

For reference, the issues workflow is described in the contribution guidelines.

requested review from @rsokolewicz

assigned to @gdenes

added 2 commits

• 2126213b - 1 commit from branch main
• cd4dd46c - SE-632: Add tutorial

Compare with previous version

added 2 commits

• 616b1268 - 1 commit from branch main
• 73c19222 - SE-632: Add tutorial

Compare with previous version

nice. A general question though:

the device overrides does not use the device parameter names, but the factory kwarg names. And they do not match all the time. If you want to change the integration time of a Measure gate, you either change the device element:

q0.measure.integration_time(200e-9)

or if you want to change it on a Gate basis:

Measure("q0", acq_duration=200e-9)

(for a transmon element this is the only time that they don't match)

Should we tell that to the user, or pretend that we use device parameter names?

I added a note on this. Hopefully it is enough.

resolved all threads

added 1 commit

• aab19136 - SE-632: Grammatical fixes from MR feedback

Compare with previous version

added 1 commit

• 6719f4e1 - SE-632: Add notes on irregular keys

Compare with previous version

added 11 commits

• 6719f4e1...003839f8 - 7 commits from branch main
• 62ab4d87 - SE-632: Add tutorial
• 32946a38 - SE-632: Grammatical fixes from MR feedback
• 8280ff91 - SE-632: Add notes on irregular keys
• aa056575 - SE-632: Change the tutorial, simpler schedule

Compare with previous version

added 1 commit

• c89f8438 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

approved this merge request

added 10 commits

• c89f8438...941ee45e - 5 commits from branch main
• 4fa1b693 - SE-632: Add tutorial
• e5164ce3 - SE-632: Grammatical fixes from MR feedback
• b1aedd24 - SE-632: Add notes on irregular keys
• 54474cfa - SE-632: Change the tutorial, simpler schedule
• 239e1647 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

added documentation label

enabled an automatic merge when all merge checks for 239e1647 pass

canceled the automatic merge

merged