Add support for fine_delay in QTM instructions

Explanation of changes

Add arguments fine_start_delay_ps and fine_end_delay_ps to certain operations that can run on a QTM. These delays do not affect the scheduled time, they only affect an argument in the final Q1ASM instruction, which can shift the actual execution of the instruction by a small amount of time.

Other solutions that were considered and rejected were:

• Allow MarkerPulse and TriggerCount to have sub-ns start times and durations: this would be very difficult to implement, and might break existing code that tries to align operations on a 1 ns grid.
• New operations specifically for the QTM: easy to implement, but slightly harder to find for users, and might cause confusion with the existing operations.

---

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.