feat: Expressions without parameters have improved compatibility with numpy.

[MarquessV]

Description

Closes #1682.

This implements the numpy array protocol by leaning on quil-rs expression simplification to get a numpy compatible number from the expression, if possible. If not, we still fallback to the default numpy behavior as to not break existing code.

Checklist

• The PR targets the master branch
• The above description motivates these changes.
• The change is atomic and can be described by a single commit (your PR will be squashed on merge).
• All changes to code are covered via unit tests.
• Parameters and return values have type hints with PEP 484 syntax.
• Functions and classes have useful Sphinx-style docstrings.
• (New Feature) The docs have been updated accordingly.
• (Bugfix) The associated issue is referenced above using auto-close keywords.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
7185	6330	88%	87%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
pyquil/paulis.py	98%	🟢
pyquil/quilatom.py	83%	🟢
TOTAL	91%	🟢

updated for commit: b4b6ac0 by action🐍

[bramathon]

Can we use np.isclose with a fairly moderate threshold here? Perhaps 1e-8?

[mhodson-rigetti]

I'd thought about this too but decided it wasn't necessary; if the inputs are all real, imag == 0.0 in all of the inputs and there are no complex operations I can think of that would accumulate a rounding error. So I'd be inclined to leave it unless you have a specific case that would trip it.

[MarquessV]

@bramathon Any thoughts on the above? Just want to make sure before I merge as-is.