chore(ci): Upgrade GitHub Actions artifact actions to latest versions

[rusackas]

User description

Summary

This PR upgrades the GitHub Actions artifact upload/download actions to their latest versions across all workflows.

Changes

• actions/upload-artifact@v4 → @v5 (6 occurrences)
• actions/download-artifact@v5 → @v6 (4 occurrences)

Benefits

The new versions include:

• Performance improvements: Faster artifact uploads and downloads
• Better compression: Reduced artifact sizes saving storage and bandwidth
• Improved reliability: Better error handling and retry logic
• Bug fixes: Various issues resolved since previous versions
• New features: Support for latest GitHub Actions features

Affected Workflows

• superset-e2e.yml - Cypress and Playwright E2E tests
• superset-extensions-cli.yml - Extensions CLI testing
• superset-frontend.yml - Frontend build and testing
• superset-playwright.yml - Playwright tests

Testing

• All workflows use the same artifact action patterns
• These are widely-used, stable GitHub Actions maintained by GitHub
• The upgrade path is straightforward with no breaking changes

References

• upload-artifact v5 release notes
• download-artifact v6 release notes

🤖 Generated with Claude Code

---

CodeAnt-AI Description

Upgrade CI artifact upload to v5 and download to v6 for faster, smaller, and more reliable artifacts

What Changed

• Artifact upload steps now use upload-artifact@v5 and download steps use download-artifact@v6 across CI workflows
• Updated workflows: superset-e2e.yml, superset-frontend.yml, superset-playwright.yml, superset-extensions-cli.yml
• Users will see faster artifact transfers, smaller uploaded artifact sizes, and fewer failures or retries when CI jobs store or retrieve artifacts

Impact

✅ Faster artifact uploads and downloads
✅ Reduced artifact storage and bandwidth
✅ Fewer CI workflow failures during artifact handling

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai-for-open-source]

CodeAnt AI is reviewing your PR.

[bito-code-review]

Bito Automatic Review Skipped - Files Excluded

Bito didn't auto-review this change because all changed files are in the exclusion list for automatic reviews. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.
You can change the excluded files settings here, or contact your Bito workspace admin at evan@preset.io.

[codeant-ai-for-open-source]

CodeAnt AI finished reviewing your PR.