Post-processors are not able to run when skip_create_ami is set

#### Community Note

Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

#### Description

Post-processors are not run when `skip_create_ami` is `true`.

#### Use Case(s)

I am trying to run some EC2 instances to build and download an artifact and then add it to the manifest with the `artifice` and `manifest` post-processors. But they don't appear to work when I don't want to keep the AMI with `skip_create_ami`.

#### Potential configuration

```
source "amazon-ebs" "ubuntu-jammy-arm64" {
ami_name = "package-${source.name}-ruby"
ssh_username = "ubuntu"
instance_type = "m6g.xlarge"
source_ami = data.amazon-ami.ubuntu-jammy-arm64.id
skip_create_ami = true
force_run_post_processors = true
}
```

#### Potential References