chore(percy): add percy context to finalize job

[flotwig]

• Closes

User facing changelog

Additional details

• We recently rotated tokens and as part of that, noticed that the PERCY_TOKEN was in both test-runner:percy and main env. After removing it from main env percy-finalize started to fail open: https://app.circleci.com/pipelines/github/cypress-io/cypress/42503/workflows/3ee274a4-9f4e-4aaa-aa25-783973088d7b/jobs/1767086
• Adding this context should restore the Percy functionality.
• See here that PERCY_TOKEN is set: https://app.circleci.com/pipelines/github/cypress-io/cypress/42515/workflows/3ca0074a-28ad-459a-9c12-a08d4db1c9a8/jobs/1767748?invite=true#step-111-9

Steps to test

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

39609 • 0 • 3371 • 0 • 0

---

Run details

Project	cypress
Status	Passed
Commit	ba957ce
Started	Aug 25, 2022 10:59 PM
Ended	Aug 25, 2022 11:13 PM
Duration	14:11 💡
OS	Linux Debian - 11.3
Browser	Multiple

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[flotwig]

I think percy-finalize is only failing because develop is missing a finalized Percy build... going to merge 🤞