Add ekore_py

[AkshatRai07]

A step for #519
In this PR we:

• ekore_py crate, which exposes ekore crate using PyO3 and build the lib using maturin.
• Expose anomalous_dimensions and operator_matrix_elements as Python functions.

TODO

• Expose necessary functions and constants.
• Add guards.
• Add tests.
• Add CI.
• Add CD.
• Add doc-strings.
• Explore removal of duplicate code.
• Add Changelog entry.

[AkshatRai07]

Doubt, what should we name this python library?

[Copilot]

Pull request overview

Adds a new ekore_py crate intended to provide Python bindings for ekore via PyO3, and wires it into the workspace/release metadata while updating crate READMEs to reference the new component.

Changes:

• Introduces a new crates/ekore_py package with an initial PyO3 module scaffold plus Python packaging metadata (pyproject.toml).
• Adds pyo3 to workspace dependencies and updates Cargo.lock accordingly.
• Updates framework documentation and release crate list to include ekore_py.

Reviewed changes

Copilot reviewed 10 out of 11 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
crates/release.json	Adds ekore_py to the crate release list.
crates/ekore/README.md	Mentions the new ekore_py crate in the framework list.
crates/ekore_py/src/lib.rs	Adds initial PyO3 module scaffold (currently a template function).
crates/ekore_py/README.md	Introduces README for the Python binding crate.
crates/ekore_py/pyproject.toml	Adds maturin-based Python build metadata for ekore_py.
crates/ekore_py/Cargo.toml	Adds new Rust crate manifest for the PyO3 cdylib.
crates/ekore_capi/README.md	Mentions ekore_py in the framework list.
crates/eko/README.md	Mentions ekore_py in the framework list.
crates/dekoder/README.md	Mentions ekore_py in the framework list.
Cargo.toml	Adds pyo3 to workspace dependencies.
Cargo.lock	Updates lockfile format/version and adds PyO3 dependency graph entries.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[felixhekhorn]

Doubt, what should we name this python library?

I guess there are two options: ekore_py (as in PineAPPL https://github.com/NNPDF/pineappl/tree/master/pineappl_py ) or ekore_pyapi (as in NeoPDF https://github.com/QCDLab/neopdf/tree/master/neopdf_pyapi) - I'm fine with either ... maybe the latter is slightly more consistent?

[AkshatRai07]

The crate name will be ekore_py only, I was asking the name of the python library. For eg. it's the eko crate but the python project is eko-rs (hence pip install eko-rs) and library is ekors (hence import ekors). For neopdf_pyapi it's neopdf-hep and neopdf, for pineappl_py it is pineappl and pineappl (both are same).