Add frontend API functions for `disentangle-SWAP/CNOT` passes

[paul0403]

Two more circuit transformation passes, disentangle-SWAP/CNOT, were added in #1154 , but the frontend APIs (aka their parallel of catalyst.passes.cancel_inverse/merge_rotations) were not created (due to lack of time: it was end-of-year and people were going off to vacations 😅 ).

[josh146]

@paul0403 how much work is involved here if we wanted to get this included in the 0.10 release?

[dime10]

@paul0403 how much work is involved here if we wanted to get this included in the 0.10 release?

I believe @erick-xanadu actually has a PR that allows the passes to be invoked from the frontend (#1407)

[paul0403]

@paul0403 how much work is involved here if we wanted to get this included in the 0.10 release?

I would actually like to clean up these frontend pass applications when I get back. Now with Erick's Pass class and apply_pass function all the specific APIs can just call that, instead of manually binding primitives. Of course I'm also happy if @erick-xanadu wants to do this now : )

For the release, a quick workaround is just copy-pasting what cancel_inverses and merge_rotations did, which is quite minimal work.

[josh146]

Hey Paul, I just wanted to check if this was still relevant?

[paul0403]

Hey Paul, I just wanted to check if this was still relevant?

We have the general apply_pass entry point now, so this is not as urgent. I'm not sure whether we want disentangle-CNOT/SWAP to have their own specialized entry point (like cancel inverses and merge rotations). Thoughts on this?