Gap in publishing resource artifacts for new versions

#### Overview of the Issue

This morning we experienced a small (on the order of minutes probably) gap where the new version (1.0.3) was published and being used by `packer init` but the resource artifacts weren't yet available, resulting in the following error in our build system:
```
could not get sha256 checksum file for github.com/hashicorp/amazon version 1.0.3. Is the file present on the release and correctly named ? GET https://github.com/hashicorp/packer-plugin-amazon/releases/download/v1.0.3/packer-plugin-amazon_v1.0.3_SHA256SUMS: 404 []
```

I believe the comment on [this commit](https://github.com/hashicorp/packer-plugin-amazon/commit/3a42df0bdc0c729194d717b9ba0971f171088cad) is referring to the same issue.

We don't want to have to pin versions, as getting any bug fixes are important, but we'd also like to avoid spurious errors in our build systems. Is there some gap in the release process for this plugin?

Thanks! We appreciate any help 🙏