Add semantic classNames and data-testid attributes to critical interactive controls

[Copilot]

This PR adds semantic classNames and data-testid attributes to critical buttons and controls across the Pulse UI client to enable easier styling and future Playwright-based testing.

What Changed

Added 22 semantic identifiers to key interactive elements across major pages, focusing on the most important 4-5 controls per page as requested:

SQL Editor Page

• Run buttons: Added sql-run-all-button, sql-run-selected-button, sql-run-line-button classes with corresponding data-testid attributes
• Share functionality: Added semantic classes to share buttons for better identification
• SQL Editor component: Added sql-code-editor class to the main editor
• Result grid: Added sql-result-grid class and data-testid to the query results table

Navigation Components

• Main navigation: Added semantic classes to Dashboard, SQL Editor, and Connections nav buttons
• User controls: Added classes to help, user menu, login, and theme toggle buttons
• All navigation elements include both semantic classNames and data-testid attributes for comprehensive testing support

Dashboard Management

• Dashboard actions: Added semantic classes to Add Dashboard, Edit, Favourite, and Popout buttons
• Each button includes descriptive class names following the pattern dash-{action}-button

Connection Management

• Connection controls: Added classes to Add Connection, Save/Test, and connection type buttons
• Follows consistent naming pattern conn-{action}-button

Toast Notifications

• Added toast-notification semantic class to the Notyf notification system

Technical Implementation

• Minimal changes: Only added className and data-testid props without modifying existing functionality
• Type safety: Updated AGrid component props to properly accept className and data-testid attributes
• Build impact: Minimal bundle size increase (+375B) with no performance regression
• Consistency: Used descriptive, kebab-case naming convention throughout

Benefits

1. Easier Styling: CSS classes can now target specific UI elements without relying on complex selectors
2. Test Automation: data-testid attributes enable robust Playwright test automation
3. Maintainability: Semantic names make the codebase more self-documenting
4. Future-proof: Establishes foundation for consistent UI testing patterns

The implementation follows best practices for test automation while maintaining the existing UI behavior and visual design.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.