Architect prunes static files before deploying CloudFormation stack

[gimdongwoo]

Thank you for helping out! ✨

We really appreciate your commitment to improving Architect

To maintain a high standard of quality in our releases, before merging every pull request we ask that you've completed the following:

• Forked the repo and created your branch from main
• Made sure tests pass (run npm it from the repo root)
• Expanded test coverage related to your changes:
  • Added and/or updated unit tests (if appropriate)
  • Added and/or updated integration tests (if appropriate)
• Updated relevant documentation:
  • Internal to this repo (e.g. readme.md, help docs, inline docs & comments, etc.)
  • Architect docs (arc.codes)
• Summarized your changes in changelog.md
• Linked to any related issues, PRs, etc. below that may relate to, consume, or necessitate these changes

Please also be sure to completed the CLA (if you haven't already).

Learn more about contributing to Architect here.

Thanks again!

Purpose

I discovered that during the arc deploy process, the CloudFormation stack was deployed before the static assets were uploaded.
A service error occurs because the static asset cannot be found.
Upon investigating the issue, I found that code changes had been made to address this in the following issue:
architect/architect#1416.
However, I do not understand why a fingerprint is required, as it works well without fingerprint check.
I don't use fingerprint option. I use Remix with architect, in which case the fingerprint option is not available.
I used the patch-package tool to modify this part, and I confirmed that my service operates as intended afterward.

Thanks!

[CLAassistant]

All committers have signed the CLA.