CI/CD: simplify artifact step #44
Description
Ref #36 (comment)
With #36 we persist relevant artifacts so that the subsequent deploy step can use them to deploy the website. However, the current approach of listing all of the file paths that are referenced in the app's spin.toml is fragile and a maintenance burden. Look into another approach while still maintaining the overall flow of "build artifacts, deploy artifacts" in the pipeline.