chore(e2e): using updated repo secret, new Cypress project id

[rusackas]

SUMMARY

Our old key was in the codebase... le sigh.

This PR uses a new Cypress project id, and a new repo secret already put in place by ASF. We'll need to merge this to continue making changes on the Cypress dashboard side.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A

TESTING INSTRUCTIONS

Hopefully we can kick off a manual test run with Dashboard recording. Otherwise, merge and see if it works there!

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[rusackas]

@mistercrunch what's the way to manually trigger a test run with Cypress dashboard, again? I'd like to do that here if possible.

[mistercrunch]

@rusackas to trigger, on this page -> https://github.com/apache/superset/actions/workflows/superset-e2e.yml, hit "Run Workflow"

Can also use the CLI, something like gh workflow run superset-e2e.yml --ref cypress_when_needed --field use_dashboard="true" --field pr_id="29077"

Where --ref points to a remote branch on apache/

[rusackas]

Added that to the wiki here: https://github.com/apache/superset/wiki/GitHub-Actions-Tips-&-Tricks