Fix Storybook published messaging

[tevanoff]

This fixes a couple of issues with the Storybook published messaging.

1. Logging this from the publishBuild step meant that sometimes the ctx.build used to construct the message was in an early stage (like PASSED) without component and story information, resulting in a message like:

✔ Storybook published
We found undefined components with undefined stories.

2. This is also logged from the verifyBuild step under certain conditions (like with exit-once-uploaded), resulting in duplicate messaging like:

✔ Storybook published
We found undefined components with undefined stories.

✔ Storybook published
We found 19 components with 221 stories.

How to Test

• With the canary version, commit some changes and run builds with various flags including with and without exit-once-uploaded and only-changed.

📦 Published PR as canary version: 10.9.6--canary.920.7904727338.0

✨ Test out this PR locally via:

npm install [email protected]
# or 
yarn add [email protected]

[ethriel3695]

@tevanoff
How can I test this?

Can I reference the Canary build and then what?
How can I trigger this use case?

[tevanoff]

@tevanoff How can I test this?

Can I reference the Canary build and then what? How can I trigger this use case?

@ethriel3695 I added some info about testing to the PR message. Those two flags seemed to affect the behavior of the output in my testing.

[ethriel3695]

@tevanoff I think this did it!
I ran the Action with the latest and saw the undefined stories output.

Now on the canary:

Collecting Storybook metadata
Collected Storybook metadata
    → ; no supported addons found
Initializing build
Initialized build
    → Build 17 initialized
Publish your built Storybook
    → Validating Storybook files
Publishing your built Storybook
    → Calculating file hashes
Publishing your built Storybook
    → Starting publish
    → [                    ] 0%
Publish complete in 9 seconds
    → Uploaded 168 files (28.73 MB)
Verifying your Storybook
    → This may take a few minutes
    → [*                   ]
⚠ TurboSnap not available for your account
To ensure your project is fully setup and baselines are properly established,
TurboSnap is not available until at least 10 builds are created from CI and one
of those builds is accepted.
ℹ Review your TurboSnap availability on the Manage screen:
https://www.chromatic.com/manage?appId=65bdd147c425b429f5968c04
✔ Storybook published
We found 14 components with [23](https://github.com/enhanced-dev/blog-tutorial-remix/actions/runs/7880523801/job/21502694657#step:6:24) stories.
ℹ View your Storybook at https://65bdd147c4[25](https://github.com/enhanced-dev/blog-tutorial-remix/actions/runs/7880523801/job/21502694657#step:6:26)b4[29](https://github.com/enhanced-dev/blog-tutorial-remix/actions/runs/7880523801/job/21502694657#step:6:30)f5968c04-bqslfbpzzu.chromatic.com/

It looks like this is what we want.

[ghengeveld]

I don't see why PASSED builds would not have component and story information. They were tested after all.

[ghengeveld]

🚀 PR was released in v10.9.5 🚀