Publish 2025-1-err2 #274

What

Cut and publish errata release 2025-1-err2 (EF release 1.0.2), reflecting
the ISO/IEC FDIS 20151-1 terminology and bibliography alignment from #267,
following review through the Eclipse Foundation Release Review and
Specification Committee Ballot for 2025-1-RC5.

Steps

• Specification Committee Ballot approval (not required, but accepted by Spec Committee on Sept. 9, 2026)
• Merge the release-prep PR (release/2025-1-err2 → main)
• Tag the chore: publish 2025-1-err2 commit as 2025-1-err2 and push the tag
• Re-run the Auto-Publish workflow so it picks up the new tag
• Verify https://eclipse-dataspace-protocol-base.github.io/DataspaceProtocol/2025-1-err2/ renders correctly
• Update Eclipse PMI with EF release 1.0.2 (and backfill 1.0.1 for 2025-1-err1)

⚠️ Merge method for the release-prep PR

This PR must be merged with "Rebase and merge", not "Squash and merge".

Same reason as always: the release-prep branch carries two commits on
purpose — one setting specStatus: "base" and publishDate (the commit the
tag must point to), one reverting to "unofficial". Squashing collapses
both into one final-state commit and drops the "base"-status snapshot the
tag needs. This has happened twice already for this project (2025-1-RC4 /
PR #206, and 2025-1-RC5 / PR #270) — both had to be reverted and redone as
individually preserved commits (see #270's history for the most recent
example).