chore: Attempt at making execute_llvm editable in local uv development (#737)

This is an attempt at avoiding `uv` from caching `execute_llvm` and
reflecting new changes to the package.

As part of this I updated various dependencies:

- `maturin 1.4 -> 1.7.7`, since [this
issue](https://www.github.com/PyO3/maturin/issues/2346) seemed related.
- `pyo3 0.19 -> 0.23`, and updated the bindings syntax.

The change that actually worked was removing the unversioned
"execute_llvm" entry in the main package's dependencies. Since we
manually install it using `maturin develop`, it now ensures that changes
get re-compiled and reflected on the python runtime.

drive-by: Update `execute_llvm` to read packages instead of hugrs, so we
can pass it guppys with quantum primitives.

Author: aborgna-q

Cargo.lock

@@ -22,7 +22,7 @@ missing_docs = "warn"
 debug_assert_with_mut_call = "warn"
 
 [workspace.dependencies]
-pyo3 = "0.19.0"
+pyo3 = "0.23.3"
 serde_json = "1.0.111"
 cargo_toml = "0.20.4"
 thiserror = "2.0.6"

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "execute_llvm"
-version = "0.2.1"
+version = "0.2.3"
 edition.workspace = true
 homepage.workspace = true
 repository.workspace = true
@@ -15,7 +15,7 @@ name = "execute_llvm"
 crate-type = ["cdylib"]
 
 [dependencies]
-hugr = {workspace = true, features = ["llvm"]}
+hugr = { workspace = true, features = ["llvm"] }
 inkwell.workspace = true
 pyo3.workspace = true
 serde_json.workspace = true

execute_llvm/Cargo.toml

@@ -10,7 +10,7 @@ classifiers = [
 dynamic = ["version"]
 
 [build-system]
-requires = ["maturin>=1.3,<2.0"]
+requires = ["maturin>=1.7.7,<2.0"]
 build-backend = "maturin"
 
 [tool.maturin]