feat: add independent PDP pinning

[galargh]

Related to #121

This exposes PDP as an independently pinnable component of foc-devnet. It defaults to using the version bundled with filecoin-services. In particular, the ability to pin pdp independently will be used to test partial ugprade scenarios.

Testing

• CI
• Nightly Build
  • 🟢 https://github.com/FilOzone/foc-devnet/actions/runs/29686229848
  • 🟢 https://github.com/FilOzone/foc-devnet/actions/runs/29687672236

Questions

1. For stability profile, should pdp be pinned to latest stable release of pdp, or the version used by latest stable release of filecoin-services?

[rvagg]

For stability profile, should pdp be pinned to latest stable release of pdp, or the version used by latest stable release of filecoin-services?

My initial reaction here is filecoin-services, we always bump through there, but we did have one release where we moved it separately. @rjan90 can you weigh in on this one? did we change our release process so that what's the submodule in filecoin-services is what's deployed? Ultimately I think it'll only matter for a small window, but a small window is where it might matter the most.

[rjan90]

My initial reaction here is filecoin-services, we always bump through there, but we did have one release where we moved it separately. @rjan90 can you weigh in on this one?

I believe the separate rollout was the PDP v3.4.0 / filecoin-services v1.2.1 hotfix scenario:

• PDP v3.4.0 was deployed independently, upgrading the live PDPVerifier proxies from v3.2.0 to v3.4.0.
• That release removed the USDFC_SYBIL_FEE() getter, while the deployed FWSS v1.2.0 implementation still depended on it.
• filecoin-services v1.2.1 was then released as a compatibility hotfix. It upgraded FWSS to use a local 0.1 USDFC constant instead of calling the removed getter; it did not perform the PDP upgrade itself.
• Because v1.2.1 was cut from the v1.2.x release branch, its PDP submodule still pointed to v3.2.0 even though the live PDP proxies were already running v3.4.0. This mismatch is described in filecoin-services #493.
• The filecoin-services main branch was subsequently synchronized with the final PDP v3.4.0 tag in #489, and that pin was included in the next normal stable release, v1.3.0.

[rvagg]

approved pending some input from @rjan90 to the question of which is the authority; I think fwss version probably
also pls land with conventional commits style commit message(s) when you do land it

[galargh]

I rewrote the commits and, more importantly, the title in conventinal commit style so that when it lands it uses it.

Pinning pdp in stability to version from filecoin-services then. I think it better describes the desired sets. Then, we'll test the mix-bag by taking filecoin-services from stability and pdp from frontier.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.