pdpv0: pdpv/1.2.0 release before push to use `pdpv0-main`

[BigLep]

Done Criteria

1. We have a pdpv1.2.0 tag that includes:
   • pdpv0: Add SP-to-SP piece fetch endpoint #828
     -feat(pdp): add SP-to-SP piece pull endpoint #864
   • pdpv0: Clean-up terminated data sets (improve existing and support externally-terminated) #871
     • fix: connect unrecoverable fails to service termination #914
   • pdpv0: stuck settlement transactions after confirmed on-chain but failed DB update #922
   • pdpv0: Obsolete PDPv0_Prove tasks should be discarded #918
     • pdp: reset to next proving period when challenge epoch is in the future #934
   • use background context #846
   • fix(pdp): detect contract reverts and exclude terminated datasets from scheduling #869
   • fix: notify task scheduling #867
   • Consult chain for watcher rail ids #898
2. @TippyFlitsUK has validated the release for a couple of days on his SP
3. PDP SPs have been advised to update (e.g., announcement in Slack)

Why Important

1. Gets critical improvements/fixes before we call us "Mainnet Ready"
2. Precondition for getting SPs to start using pdpdv0-main in the future.

[rjan90]

I added #867 and #869 to the list. Since these should help fix the issue we saw starting on Friday.

[rjan90]

Bumping the release version here to pdpv1.2.0, since we issues a pdpv1.1.1 release due to: FilOzone/filecoin-services#380

[BigLep]

@snadrus : per 2026-01-15 conversation, I thought I heard from you say that a recent pdp Cruio tag actually has the necessary changes. As a result, should we be doing development on pdpv-main and cutting "PDP releases" for FOC GA from pdpv0-main or would you advise to continue to develop on and cut releases from pdpdv0 (until we make the concerted effort to get back to main ASAP after GA)?