E2E tests for permission-based CRUD operations on secrets

This issue involves creating comprehensive End-to-End (E2E) tests for GitLab Secrets Manager to verify permission-based CRUD (Create, Read, Update, Delete) operations through the UI. The testing scope has expanded significantly due to the complex permission matrix that needs validation.

Key Requirements

Permission Matrix Testing:

• User roles: Different user permission levels
• Group roles: Various group membership roles
• Member roles: Specific member-level permissions
• Cross-combinations: All permutations between User/Role/Group/MemberRole

CRUD Operations to Test:

• Create: Verify users can/cannot create secrets based on permissions
• Read: Test secret visibility and access controls
• Update: Validate modification permissions
• Delete: Confirm deletion authorization

UI Coverage:

• Test all permission scenarios through the GitLab web interface
• Verify proper error messages for unauthorized actions
• Ensure UI elements show/hide based on user permissions

Complexity Factors (Weight 5 Justification)

1. Multiple permission combinations requiring individual test scenarios
2. UI state validation for each permission level
3. Cross-role testing between different user types
4. Negative testing for unauthorized operations
5. Test data setup for various user/group configurations

Implementation Considerations

• Create test fixtures for different user/group/role combinations
• Implement reusable permission validation helpers
• Design parameterized tests to cover all scenarios efficiently
• Include both positive and negative test cases
• Ensure proper test isolation and cleanup

This comprehensive testing approach ensures GitLab Secrets Manager's permission system works correctly across all user scenarios in the Beta release.