Stub pyi file autogen using pyo3-stub-gen

[zao111222333]

Follow up #237
As pyo3-stub-gen can use the pyo3's signature information for pyi file (Jij-Inc/pyo3-stub-gen#135), it will be more useful to auto generate pyi files.

Here is the new version of auto-generated egobox.pyi, by command

cargo run --package egobox --bin stub_gen

There are two tasks to be done:

• Waitting for Avoid IntoPyObjectExt::into_bound_py_any for None value Jij-Inc/pyo3-stub-gen#188 to be merged in the new version of pyo3-stub-gen
• pyo3-stub-gen's signature feature require pyo3 0.23 and above, so I upgrade it to 0.24. Pls help me review the modifcations

BTW, thx a lot for your contribution for SMT, which I find is so efficient in my researches!

[relf]

Hi, thanks for your interest (you mention SMT, out of curiosity do you use GPX?).
At the moment, as discussed in #237, I prefer to wait for the update in pyo3-stub-gen before merging this.
In the meantime, I will be happy to accept a PR with just the updated egobox.pyi, thanks!

[zao111222333]

you mention SMT, out of curiosity do you use GPX?

While, I have tried GPX but I found MFKPLSK is impressive accurate. GPX is good enough compared to other implementations (such as Gpy, GpyTorch) in my scenario, but MFKPLSK is the best one. (I can put my data and comparison with a colab project)
I really want to figure out MFKPLSK's mechanism, and then I can have a rust version of it.

I prefer to wait for the update in pyo3-stub-gen before merging this.
In the meantime, I will be happy to accept a PR with just the updated egobox.pyi

Fully understand, I will follow up the progress of Jij-Inc/pyo3-stub-gen#188, and if that PR spent too much time, I will create a new PR with egobox.pyi only.