feat!: Update pyQuil, drop support for Python 3.8, enable support for Python 3.13

[MarquessV]

closes #18

The CI checks for Python 3.8 have been replaced with checking Python 3.12. I will update the required checks once this PR is approved.

[BatmanAoD]

The original version of this added a mypy ignore because the interface doesn't actually match the QuantumAbstractMachine defined in PyQuil, but that seems incorrect to me, so we should figure out how that divergence occurred and whether this library or PyQuil's interface needs to change.

[BatmanAoD]

The run_batch function has existed since the initial commit. Maybe we need to keep that, with the existing API, and also implement the new execute_with_memory_map_batch function?

[BatmanAoD]

I am making the APIs of both AzureQuantumComputer and AzureQuantumMachine as compatible as possible with QuantumComputer and QAM, respectively. The Azure classes still must use the AzureProgram type rather than Program or EncryptedProgram, but I've added comments explaining that, and applied a more narrow mypy exception for each function.

[jselig-rigetti]

The run_batch function has existed since the initial commit. Maybe we need to keep that, with the existing API, and also implement the new execute_with_memory_map_batch function?

Is this why run_batch was removed entirely? Would it be a problem to alias it to run_with_memory_map_batch?

Overall LGTM though 👍 don't forget to make this breaking with feat!:

[BatmanAoD]

@jselig-rigetti run_batch was removed because the memory_map format doesn't match the current format (each map value is a list-of-lists, where the "outer" list corresponds to the number of execution configurations), so making it an alias would be a breaking change anyway.