fix: docker: Dockerfile import snapshot

[vidbregar]

Related Issues

Proposed Changes

• Updates Dockerfile to default to a working snapshot endpoint

  curl -I https://snapshots.mainnet.filops.net/minimal/latest
  HTTP/1.1 503 Service Unavailable: Back-end server is at capacity
  Connection: keep-alive

    curl -I https://forest-archive.chainsafe.dev/latest/mainnet/
    HTTP/2 302
    ...

• Since 1.25.2, entrypoint script requires yes to import the snapshot

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[Stebalien]

This actually seems like a bug. We should only be prompting the user if there's actually a chain to remove.

[Stebalien]

#11582

[Stebalien]

Fixed on master, this change shouldn't be necessary anymore. Although it may help to pass --remove-existing-chain=false (which will cause an immediate failure if there's an existing change, which there shouldn't be given that the node isn't initialized).

[vidbregar]

Rebased and added the flag. Although, I'm not sure what happened to the unreleased changelog.

[Stebalien]

@vidbregar can you rebase on master and address my comment?

[Stebalien]

Thanks!