fix(sui,aptos): skip tarring cwd when ContractsDir is empty

[Fletch153]

Summary

newSui and newAptos in framework/components/blockchain/ unconditionally call filepath.Abs(in.ContractsDir) and attach the result as a testcontainers.ContainerFile. When the caller leaves ContractsDir empty (the common case for chains that do not need host contracts copied in), filepath.Abs("") resolves to the process working directory. testcontainers-go then tars that whole cwd via archive/tar to copy into the container.

In integration-tests the cwd is a live test working directory — log files, db dumps, artifact collectors — actively being appended to while the container starts. If a file grows between tar.FileInfoHeader (header size from os.Stat) and the subsequent io.Copy, stdlib's tar.Writer returns ErrWriteTooLong and testcontainers surfaces:

create container: created hook: can't copy <cwd> to container:
error compressing file: archive/tar: write too long

Evidence — real CI failure

chainlink run 24372896623, job 71183740665, test Test_CCIPTokenTransfer_Sui2EVM_BurnMintTokenPool:

ctf_provider.go:230: Attempt 1/10: Failed to start CTF Sui container:
  create container: created hook: can't copy
  /home/runner/_work/chainlink/chainlink/integration-tests/smoke/ccip to container:
  error compressing file: archive/tar: write too long
ctf_provider.go:230: Attempt 2/10: Failed to start CTF Sui container: ...
ctf_provider.go:230: Attempt 3/10: Failed to start CTF Sui container: ...

Cwd printed (/home/runner/.../integration-tests/smoke/ccip) matches the predicted race target exactly — that directory is actively written by deployment/logger.SingleFileLogger (relative logs/ dir, autoFlushWriter syncs on every write) while the container starts.

Cause chain (verified link-by-link)

1. Caller passes empty ContractsDir — chainlink-deployments-framework/chain/sui/provider/ctf_provider.go:199-206 builds blockchain.Input{Type: TypeSui, ...} with no ContractsDir field. CTFChainProviderConfig exposes no such knob.
2. filepath.Abs("") = cwd — Go stdlib contract. sui.go:98 on main: absPath, err := filepath.Abs(in.ContractsDir).
3. cwd attached as ContainerFile — sui.go:153-158: Files: []ContainerFile{{HostFilePath: absPath, ContainerFilePath: "/"}}, unconditional.
4. testcontainers-go tars the host dir — lifecycle.go:146-172 defaultCopyFileToContainerHook walks HostFilePath; Go's archive/tar.Writer.Write returns ErrWriteTooLong when body bytes exceed header Size.
5. Retry absorbs most occurrences — chainlink-deployments-framework/chain/sui/provider/ctf_provider.go:152,226 wraps NewBlockchainNetwork in retry.Do with retry.Attempts(10), retry.Delay(1s). Most runs self-heal by attempt 2-3; occasional hard failures exhaust the retry budget.

Fix

Gate the ContainerFile entry on in.ContractsDir != "":

• Callers that explicitly pass a directory keep identical copy-to-container behaviour.
• Callers that need no host files (the current default for e.g. CCIP Sui smoke tests) no longer tar a busy cwd, eliminating the stat→stream race.

Applied to both sui.go and aptos.go — they share the identical shape and bug. Solana (solana.go) intentionally untouched: every Solana caller sets ContractsDir explicitly (Solana validator requires .so artifacts mounted at boot), so the race path is never exercised there.

Safety analysis

• Non-empty ContractsDir callers: identical behaviour, same filepath.Abs + ContainerFile entry.
• Empty ContractsDir callers: req.Files = nil. testcontainers-go hook loops for _, f := range files — zero iterations on nil, no container-side state change. Verified in testcontainers-go@v0.41.0/lifecycle.go:151.
• Org-wide audit of TypeSui/TypeAptos callers returned 3: chainlink-deployments-framework Sui provider, chainlink-deployments-framework Aptos provider, chainlink-aptos/integration-tests/ccip/ccip_deployment_test.go. None pass a ContractsDir. The empty path isn't a documented default — the struct comment `toml:"contracts_dir" comment:"Solana's contracts directory"` explicitly scopes the field to Solana. The cwd-tarring was a latent side-effect of reusing the Solana-shaped field for Sui/Aptos, not a feature.
• Aptos/Sui containers don't consume tarred cwd contents regardless: newSui runs sui start --force-regenesis --with-faucet (stock validator + faucet), newAptos runs aptos node run-local-testnet. Neither reads files from / inside the container. Contract publishing happens host-side via sui client publish / aptos move publish over RPC against the running node.

Test Plan

• go build ./components/blockchain/... clean
• go vet ./components/blockchain/... clean
• CI green on this PR (TestAptosSmoke, TestSolanaSmoke, TestSmoke, TestChaos, lint, vuln, ~30 checks total all passing)
• Downstream verification: chainlink PR #22011 bumps CTF to this branch's HEAD. Local go build ./... passes in chainlink/deployment and chainlink/integration-tests. Full chainlink CI pending post-merge bump.

Notes

No behaviour change for anyone who was already setting ContractsDir. Draft until downstream chainlink verification CI confirms zero archive/tar: write too long retry lines in Sui CCIP smoke tests.