Codify 1.3.0 smoke test scenarios as optional foc-devnet scenarios

## Context

The [1.3.0 frontier smoke test](https://github.com/FilOzone/filecoin-services/issues/513) manually exercised a comprehensive set of lifecycle paths (see the "What Was Exercised" and "Repeatable Shape" sections). These should be codified as foc-devnet scenarios so we can confirm we don't regress in future releases.

Note: [foc-devnet issue #113](https://github.com/FilOzone/foc-devnet/issues/113) already tracks validation of pricing/termination/calldata changes in devnet. This issue is specifically about codifying the broader smoke test scenarios from the 1.3.0 report as repeatable, optional foc-devnet scenario scripts — covering the full lifecycle including abandonment, negative/security edge cases, and cross-system state validation.

## Key scenarios to codify

From the smoke report's "Repeatable Shape" section:
1. Create/fund/upload, 40-piece add, repeated adds forcing lockup replenish
2. Piece removal with proving period flush
3. SP-relayed termination and direct on-chain termination
4. Normal cleanup verification (FWSS, PDP, FilecoinPay, Curio state)
5. Abandonment flow (stop SP, wait past inactivity, third-party cleanup)
6. Negative permission checks (unauthorized termination, malformed payloads, etc.)

## Origin

Request from [comment on the 1.3.0 smoke report](https://github.com/FilOzone/filecoin-services/issues/513#issuecomment-4634302642).