NXDRIVE-2986: Align Python client with LTS 2025

[gitofanindya]

Summary by Sourcery

CI:

• Add Nuxeo LTS 2025 to the CI test matrix

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request aligns the Python client with Nuxeo LTS 2025 by modifying the functional and unit tests workflows to include the new LTS version in the test matrix. This ensures that the client is tested against the latest LTS version.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Aligned the functional and unit tests workflows to include Nuxeo LTS 2025.	Added Nuxeo LTS 2025 to the matrix of tested versions in the functional tests workflow. Added Nuxeo LTS 2025 to the matrix of tested versions in the unit tests workflow.	.github/workflows/functional_tests.yml .github/workflows/unit_tests.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @gitofanindya - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider adding a comment to the changelog to describe the reason for this change.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

question (typo): Clarify the meaning of NXPY->

It looks like there might be a typo in NXPY->, or perhaps some information is missing. Could you clarify the intended meaning?

Suggested implementation:

- NXPY: [Please clarify what NXPY refers to, e.g., "Updated to new NXPY version with enhanced functionality"]

Ensure that the placeholder text is updated with the accurate description of what NXPY stands for and what changes were made. This will improve clarity for users reading the changelog.