[TODO] Run Create Cedar App tests with latest Canary during Release

[Tobbe]

During release we kick off a Canary CI job that publishes a new canary build. This is as close as we'll get to the next real version that'll be published.

A "normal" CI check is also run. This one will fail, because it tries to install package versions that aren't published yet.

I'd like to combine these two, especially the "Create Cedar App" step of the regular CI action, with the newest Canary package versions. This is as close as we can get to trying a full install with the packages that we're releasing I think.

I think a good approach could be:

1. Make publish-canary.yml somehow return the exact version that was published
2. Update create-cedar-app-test.yml so that you can pass it a specific version of a published package to use, instead of building and packing a local version.
3. Use an API call to trigger create-cedar-app-test.yml, passing in the newly published canary version, so that it uses that version for testing

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[Tobbe]

Since I originally wrote this issue I've updated the "normal" CI job to skip the Create Cedar App step because it would always fail. But I still think the idea in this issue is good. It'd be great to run the Create Cedar App tests with the latest canary version.