SECRETS-88 Add view git history to overview

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Overview

Greptile Summary

This PR adds commit history access to the overview page with a badge showing commit count when viewing a single environment. Users can click to navigate to the commits page from both the environment dropdown menu (multi-env view) and the commit badge (single-env view). The back link on the commits page now navigates to the overview page instead of the old secrets page.

Key Changes:

• Added commit history navigation with handleViewCommitHistory that fetches folder ID and navigates to commits page
• Implemented environment selection persistence using localStorage (overview-selected-envs-${projectId})
• Added DownloadEnvButton component for downloading .env files (single environment only)
• Enhanced dynamic secret and folder rows with delete functionality
• Improved responsive layout across multiple table row components
• Updated route schema to support environments array parameter for URL state

Implementation Quality:

• Proper permission checks using canReadCommits before allowing commit history access
• Upgrade prompt shown when pitRecovery subscription feature is not available
• Download functionality correctly merges local and imported secrets with personal overrides taking precedence
• Value escaping in download helper properly handles backslashes and quotes

Confidence Score: 4/5

• Safe to merge with minor considerations around documentation
• The implementation is solid with proper permission checks, error handling, and escaping. The code follows React best practices with hooks like useMemo and useCallback. However, the PR introduces significant new user-facing features without documentation updates (download button, commit history access), which may impact feature discoverability per custom rule guidelines.
• No files require special attention - all changes are well-structured frontend enhancements with appropriate safeguards

Important Files Changed

_{Last reviewed commit: 6f8fa4f}