Improve `__str__` and `__repr__` for `SingleQubitCliffordGate`

[NoureldinYosri]

Is your feature request related to a use case or problem? Please describe. Both the string and repr operators of SingleQubitCliffrodGate fall to its parent class which gives a confusing representaiton e.g.

>>> import cirq
>>> repr(cirq.ops.SingleQubitCliffordGate.X)
"cirq.CliffordGate.from_clifford_tableau(cirq.CliffordTableau(1,rs=np.array([False, True], dtype=np.dtype('bool')), xs=np.array([[True], [False]], dtype=np.dtype('bool')),zs=np.array([[False], [True]], dtype=np.dtype('bool')), initial_state=0))"
>>> str(cirq.ops.SingleQubitCliffordGate.X)
"cirq.CliffordGate.from_clifford_tableau(cirq.CliffordTableau(1,rs=np.array([False, True], dtype=np.dtype('bool')), xs=np.array([[True], [False]], dtype=np.dtype('bool')),zs=np.array([[False], [True]], dtype=np.dtype('bool')), initial_state=0))"

Describe the solution you'd like the representation should be simpler. For example for cirq.ops.SingleQubitCliffordGate.X it should be cirq.ops.SingleQubitCliffordGate(_clifford_tableau=cirq.CliffordTableau(1, xs=np.array([[True], [False]]), zs=np.array([[False], [True]])))

What is the urgency from your perspective for this issue? Is it blocking important work? P3 - I'm not really blocked by it, it is an idea I'd like to discuss / suggestion based on principle

[suyashdamle]

I'd like to take this one up

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days

[github-actions[bot]]

Issue closed due to inactivity.

[telescopic]

I'd like to take this up

[NoureldinYosri]

@telescopic thanks for volunteering to help with this issue. I assigned it to you.

---

on a second look, looks like this task was already assigned to @suyashdamle. If they don't wanna continue working on this you can take it on.

@suyashdamle do you wanna continue working on this or do you wanna leave it to @telescopic ?

[telescopic]

@NoureldinYosri thanks for the reply!

I was looking at a couple of other issues that had assignees from a while back - Curious on if there is some staleness limit post which issues are eligible for re-assignment? Thanks in advance!

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days

[pavoljuhas]

I was looking at a couple of other issues that had assignees from a while back - Curious on if there is some staleness limit post which issues are eligible for re-assignment? Thanks in advance!

@telescopic - we have a bot marking issues as stale after 30 days of inactivity; after that we should consider reassignment. This issue has been dormant way longer; sorry about that, sometimes lower-priority issues may fall through the cracks. If you are still interested, I'll be happy to reassign your way.

[telescopic]

@pavoljuhas - sure, please go ahead and assign this to me if that's okay!

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days