chore: Update chromatic action settings

[RayRedGoose]

Summary

Fixes: #3344

Updated inputs for chromatic.

Release Category

Infrastructure

[cypress]

Workday/canvas-kit    Run #8949

Run Properties:   Passed #8949  •  1e9903401f ℹ️: Merge c5bc13b6a786a4843fd9f1d0456a2e64d72f9240 into a8eaa7da896186d3ed4c093dccff...

Project	Workday/canvas-kit
Branch Review	fix-action
Run status	Passed #8949
Run duration	02m 57s
Commit	1e9903401f ℹ️: Merge c5bc13b6a786a4843fd9f1d0456a2e64d72f9240 into a8eaa7da896186d3ed4c093dccff...
Committer	Raisa Primerova
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	21
Skipped	0
Passing	936
View all changes introduced in this branch ↗︎

UI Coverage  21.24%
Untested elements	1529
Tested elements	410

Accessibility  99.29%
Failed rules	6 critical   5 serious   0 moderate   2 minor
Failed elements	98

[NicholasBoll]

I don't understand how this works. We already used to use a GH secret. The problem is pull requests from forks are not trusted, so GH Actions sends an empty string for any secret. This change will simply send an empty string to Chromatic.

The documentation isn't clear:

Continuous Integration

To set up CI, store your project token as the CHROMATIC_PROJECT_TOKEN environment variable or secret. The CLI automatically recognizes this variable, so you won’t have to provide it explicitly.

Here's the GHA documentation: https://www.chromatic.com/docs/github-actions/#forked-repositories

Forked repositories

GitHub secrets work at a repository level. Forked repositories will not have access to them. If you want to run Chromatic on cross-repository (forked) PRs, you’ll have to expose the projectToken by including it as plaintext in your chromatic.yml workflow file. Be aware that anyone with access to this file will be able to run Chromatic builds on your project, consuming your snapshot quota. You can reset the project token on the Manage > Configure screen at any time if you think it may have been compromised.