Added an empty pass boilerplate as a tutorial

[paul0403]

Before submitting

Please complete the following checklist when submitting a PR:

• [x] All new functions and code must be clearly commented and documented.

• [x] Ensure that code is properly formatted by running make format. The latest version of black and clang-format-14 are used in CI/CD to check formatting.

• [x] All new features must include a unit test. Integration and frontend tests should be added to frontend/test, Quantum dialect and MLIR tests should be added to mlir/test, and Runtime tests should be added to runtime/tests.

When all the above are checked, delete everything above the dashed line and fill in the pull request template.

---

Context: Added an empty pass boilerplate in the catalyst dialect that prints out hello world.

Description of the Change:

Benefits: A tutorial for the pass boilerplate infrastructure for those who want to write custom passes.

Possible Drawbacks:

Related GitHub Issues:

[sc-67240]

[github-actions[bot]]

Hello. You may have forgotten to update the changelog! Please edit doc/changelog.md on your branch with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[Qottmann]

100 extra points to fuse this with the QubitUnitaryFusion example below. I tried to create a pass using the provided example code but still struggle with the boilerplate and where to put what (I might also just represent the lower bar of potential users for this 😓 )

If I understand it correctly, most passes are organized in two separate files: one for the pattern and one for the pass. In this tutorial we only cover the pass. The QubitUnitaryFusion example covers the patterns (and briefly the pass). Would be amazing to be able to have both 😇