[placeholder] Add filecoin-pin support (team/filecoin-pin)

[BigLep]

Done Criteria

A user can use https://github.com/filecoin-project/filecoin-pin to have their generated CAR peristed.

Why Important

User/Customer

Notes

1. This is a placeholder from now until filecoin-pin is production ready and has baked for a bit. I'm creating this issue for now to have a placeholder to reference. More details will get added
2. Filecoin Pin has an example action that can be drawn from: https://github.com/filecoin-project/filecoin-pin/tree/master/upload-action
3. When this work is done, this doc should be updated https://docs.ipfs.tech/how-to/websites-on-ipfs/deploy-github-action/
4. "team/filecoin-pin" in the title is intentional so it shows up in FOC (view)

[DavidBurela]

Hi, with the Storacha IPFS service being sunset, they have suggested users migrate to Filecoin pin
https://medium.com/@storacha/an-update-on-storacha-and-important-news-for-you-and-your-data-15a5d10b7da0

Checking in on if there has been any progress on supporting filecoin pin, so that users that may be migrating from Storacha have an easier path.

[BigLep]

Thanks for reaching out @DavidBurela . We'll get this updated this week. The Filecoin Onchain Cloud working group that has been maintaining/developing Filecoin Pin needs to sync up with the IP Shipyard team who who owns this action. I agree that this would be a nice way to help Storacha users moving over to Filecoin Pin. (I don't know more specifics on dates because this is just getting figured out, and am personally heading out of town for a week and will need other team members to chime in here.)

[lidel]

@BigLep fwiw to kick-off discussion, I opened two PRs addressing the biggest problems (CAR support and separation of concerns):

• filecoin-project/filecoin-pin#410 (upstream): teaches the Filecoin Pin upload action to accept a pre-built .car file as its path input and upload it as-is (no repacking, root CID extracted from the CAR header).

• ipshipyard/ipfs-deploy-action#49 (docs-only): adds an "Archiving to Filecoin" section showing how to chain
  filecoin-project/filecoin-pin/upload-action after this action so the same CAR (and same CID) lands on Filecoin. It also includes rationale why composition is better than embedding given current filecoin-pin tooling.

Both are just a starting point for discussion -- feedback welcome!

@DavidBurela until this is figured out, fwiw you can already combine both actions today by pointing filecoin-project/filecoin-pin/upload-action at the same directory (e.g. ./dist) you pass to ipfs-deploy-action, something like:

- uses: filecoin-project/filecoin-pin/upload-action@v0
  with:
    path: ./dist
    walletPrivateKey: ${{ secrets.FILECOIN_WALLET_KEY }}
    ...

Caveats:

1. without feat(upload-action): accept pre-built .car path filecoin-project/filecoin-pin#410 the upstream action will pack its own CAR from the directory, so the Filecoin Pin IPFS root CID will most likely differ from the CID produced here (chunker defaults may diverge). After that PR is merged you can switch to path: build.car and the two CIDs will be identical.

2. If you are not self-hosting pinning (no IPFS Cluster, no Kubo), you can skip ipfs-deploy-action entirely and use filecoin-project/filecoin-pin/upload-action directly.