fix(deps): Update dependency pyarrow to v20

[cq-bot]

This PR contains the following updates:

Package	Type	Update	Change
pyarrow	dependencies	major	^14.0.2 -> ^20.0.0

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 has been generated by Renovate Bot.

[cq-bot]

⚠️ 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: poetry.lock

Updating dependencies
Resolving dependencies...


The current project's supported Python range (<3.14) is not compatible with some of the required packages Python requirement:
  - pyarrow requires Python >=3.9, so it will not be satisfied for Python <3.9

Because no versions of pyarrow match >20.0.0,<21.0.0
 and pyarrow (20.0.0) requires Python >=3.9, pyarrow is forbidden.
So, because example depends on pyarrow (^20.0.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pyarrow, a possible solution would be to set the `python` property to ">=3.9,<3.14"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers