Fix stability CI: forward init_flags to foc-devnet init and update default filecoin-services to v1.2.0

[Copilot]

Two bugs combined to cause the stability run failures: init_flags was defined as a workflow input but never forwarded to ./foc-devnet init, so --filecoin-services latesttag:v* was silently ignored. Both stability and frontier always deployed the hardcoded default — commit c79e2c6b (pre-v1.2.0) — which lacks the paginated getClientDataSets(address,uint256,uint256) that synapse-sdk now calls. The result: unknown function selector → EVM fallback → revert (exit 33).

Changes

• ci_run.yml — forward init_flags: Both ./foc-devnet init paths (Docker-cache-hit and miss) now receive ${{ inputs.init_flags }}:

  ./foc-devnet init --no-docker-build ${{ inputs.init_flags }}
  ./foc-devnet init ${{ inputs.init_flags }}

• ci_run.yml — narrow CODE_HASH to lotus/curio only: filecoin-services contains Solidity contracts compiled by Foundry at deploy time — changing its version should not bust the Lotus/Curio binary cache:

  CODE_HASH=$(echo "$VERSION_OUTPUT" | grep -E 'default:code:(lotus|curio)' | sha256sum | ...)

• config.rs — update default filecoin_services to v1.2.0: Fixes PR CI runs (which use no init_flags) by ensuring the deployed StateView includes the paginated API the synapse-sdk requires:

  filecoin_services: Location::GitTag {
      url: "https://github.com/FilOzone/filecoin-services.git".to_string(),
      tag: "v1.2.0".to_string(),
  },