feat: allow to download chalk by multiple urls

[miki725]

• [x] Followed the steps in the contributor's guide: https://crashoverride.com/docs/other/contributing#filing-the-pull-request
• [x] PR title uses semantic commit messages
• [x] Filled out the template to a useful degree
• [x] Updated CHANGELOG.md if necessary

Issue

As setup-chalk-action allows to download chalks pinned by their commit build, by only downloading chalk from a single release url, it will potentially break multi-platform builds. By attempting to download from a release url first and if failed downloading from a commit build it will allow chalk to fully function both with release and pre-release builds without requiring to update user-configs.

Testing

➜ make tests args="test_docker.py::test_multiplatform_build[valid/sample_1-True]"

[miki725]

when using pre-release build show up as:

trace: docker: no chalk binary found for TARGETPLATFORM (linux/arm64). Attempting to download chalk binary.
trace: docker: downloading chalk binary from: https://dl.crashoverride.run/chalk/chalk-0.3.6-dev-linux-arm64
trace: docker: while downloading chalk binary recieved: 404 Not Found
trace: docker: downloading chalk binary from: https://dl.crashoverride.run/chalk-commit-builds/chalk-3552c319e21f4f402854e81e778802a4e07a5a7c-linux-arm64
trace: docker: saved downloaded chalk binary for linux/arm64 to /home/runner/.local/chalk/bin/linux/arm64/chalk```

[miki725]

Better for the exception message to mention download_arch_binary?

not sure. that exception can bubble up to the user. dont think a lot of error messages show actions to users like "do X" but we can evaluate that in the long term what kind of messaging is useful on errors (not trace logs)