Preserve URI parameters on jCal round-trip

[binggao1230]

vUri.from_jcal reconstructs a vUri from a jCal property and passed the parameters positionally:

return cls(
    jcal_property[3],
    Parameters.from_jcal_property(jcal_property),
)

But vUri.__new__(cls, value, encoding=DEFAULT_ENCODING, /, params=None) has encoding as its second positional argument (positional-only, before the /). So the Parameters object was consumed as the encoding argument and the parameters were dropped, while encoding silently received a non-string. A URI value's parameters were therefore lost on a jCal round-trip, e.g. ATTACH;FMTTYPE=text/plain or CONFERENCE;FEATURE=AUDIO.

The fix passes them as the params keyword, matching every other from_jcal that targets an encoding-taking type (e.g. vText, vInline):

return cls(
    jcal_property[3],
    params=Parameters.from_jcal_property(jcal_property),
)

vUri is the only from_jcal that had this mismatch: the other positional callers (vCategory, vGeo, adr, org) take params as their second positional, so they were unaffected.

test_uri_parameters_round_trip.py covers a single parameter, multiple parameters, ATTACH/CONFERENCE real-world cases, and jCal round-trip idempotence. Full rfc_7265_jcal suite passes (1213).

Prepared with the assistance of an AI coding agent (Anthropic's Claude Opus 4.8); I reviewed and validated the change locally.

[github-actions]

Profile summary:

GitHub user: gaoflow
🟢 No concerns found with user's profile.
🟢 No concerns found with recent PR activity.
🟢 No concerns found with recent issue activity.

For a more detailed report, run `gh-profiler gaoflow`.

Full profile

GitHub user: gaoflow
🟢 No concerns found with user's profile.
   🟢 Account age: 13 years
   🟢 Profile information:
        name: Vincent Gao
        location: Paris
        email: gaobing1230@gmail.com
      Empty fields: company, blog, bio

🟢 No concerns found with recent PR activity.
   100 PRs opened in the last 21 days.
      0 opened against repos the user owns.
      0 opened against repos in publicly associated orgs.
      100 opened against external repos.

   🟢 5 of 100 external PRs closed without merging in the last 21 days.

🟢 No concerns found with recent issue activity.
   10 new issues opened in the last 21 days.
      6 opened in repos the user owns.
      0 opened in repos in publicly associated orgs.
      4 opened in external repos.

   🟢 0 external issues closed as NOT_PLANNED.
   🟢 0 external issues opened with the same title.

[read-the-docs-community]

Documentation build overview

📚 icalendar | 🛠️ Build #33632087 | 📁 Comparing 48de879 against latest (b32cbd7)

  🔍 Preview build  

22 files changed · ± 22 modified

± Modified

• 404.html
• genindex.html
• _static/webpack-macros.html
• contribute/credits.html
• contribute/index.html
• reference/changelog.html
• _modules/icalendar/cli.html
• _modules/icalendar/error.html
• contribute/documentation/build-check.html
• contribute/documentation/style-guide.html
• and 12 more...

[angatha]

Thank you for your contribution. First please follow our contributing guide. That includes, that you disclose AI use not just in the PR but also in each commit message:

In your git commit messages, you must specify both (1) which AI model and version you used, and (2) how you used it, by either including the prompts and interactions you used or summarizing them. You can automate this by using the ai-prompt-auto-commit pre-commit hook. See AI prompt automation for setup instructions.

https://icalendar.readthedocs.io/en/latest/contribute/index.html#responsible-ai-use third to last bullet point.

Note that we are working on an update of the the guideline. The relevant PR is already linked. Please have a look when it was accepted.

[angatha]

LGTM

[binggao1230]

Applied your suggested wording for the changelog — thanks for the parameter/argument correction and the clearer phrasing.

[stevepiercy]

Thank you for your contribution! Will automerge after CI checks pass.

[coveralls]

Coverage Report for CI Build 29574023220

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Coverage increased (+0.005%) to 97.906%

Details

• Coverage increased (+0.005%) from the base build.
• Patch coverage: 35 of 35 lines across 1 file are fully covered (100%).
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	13373
Covered Lines:	13098
Line Coverage:	97.94%
Relevant Branches:	813
Covered Branches:	791
Branch Coverage:	97.29%
Branches in Coverage %:	Yes
Coverage Strength:	6.85 hits per line

---

💛 - Coveralls

[niccokunzmann]

This has been released with v7.3.0.