Update Rust crate pyo3-async-runtimes to 0.27.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pyo3-async-runtimes	dependencies	minor	0.26.0 -> 0.27.0

---

Release Notes

PyO3/pyo3-async-runtimes (pyo3-async-runtimes)

v0.27.0

Compare Source

• Avoid attaching to the runtime when cloning TaskLocals by using std::sync::Arc. #​62
• Breaking: Finalize the future without holding GIL inside async-std/tokio runtime.
  Trait Runtime now requires spawn_blocking function,
  future_into_py functions now require future return type to be Send.
  #​60
• Change pyo3 downcast calls to cast calls #​65
• Use pyo3::intern! for method calls and getattr calls #​66
• Fix missing LICENSE file in macros crate by @​musicinmybrain in #​63
• Bump to pyo3 0.27. #​68

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 06:59 AM, only on Sunday and Saturday ( * 0-6 * * 6,0 ) in timezone Europe/Rome, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package pyo3-async-runtimes@0.26.0 --precise 0.27.0
    Updating crates.io index
    Updating git repository `https://github.com/platformatic/http-handler`
From https://github.com/platformatic/http-handler
 * [new ref]         f60dbc830e12b1cedae4c8a4f370bc4133a868fc -> refs/commit/f60dbc830e12b1cedae4c8a4f370bc4133a868fc
    Updating git repository `https://github.com/platformatic/http-rewriter`
From https://github.com/platformatic/http-rewriter
 * [new ref]         2c2319e6721f20a0eebcb37904d15aa411cc668f -> refs/commit/2c2319e6721f20a0eebcb37904d15aa411cc668f
error: failed to select a version for `pyo3-ffi`.
    ... required by package `pyo3 v0.27.0`
    ... which satisfies dependency `pyo3 = "^0.27"` of package `pyo3-async-runtimes v0.27.0`
    ... which satisfies dependency `pyo3-async-runtimes = "^0.27.0"` of package `python-node v1.0.0 (/tmp/renovate/repos/github/platformatic/python-node)`
versions that meet the requirements `=0.27.0` are: 0.27.0

package `pyo3-ffi` links to the native library `python`, but it conflicts with a previous package which links to `python` as well:
package `pyo3-ffi v0.26.0`
    ... which satisfies dependency `pyo3-ffi = "=0.26.0"` of package `pyo3 v0.26.0`
    ... which satisfies dependency `pyo3 = "^0.26.0"` of package `python-node v1.0.0 (/tmp/renovate/repos/github/platformatic/python-node)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the `links = "python"` value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `pyo3-ffi` which could resolve this conflict