feat: add inline security scope display for API endpoints

[JMLX42]

Description

Adds visual display of required security scopes/requirements inline for each API endpoint, addressing the long-standing issue #5062.

Motivation

Resolves #5062 - Users need to see which security scopes (OAuth2, OpenID, etc.) are required for each endpoint without clicking the padlock icon. This has been a highly requested feature for years.

Changes

• Added ScopeDisplay component to show security requirements inline next to the padlock icon
• Integrated component into OperationSummary
• Added styling for scope badges with proper visual hierarchy
• Enhanced auth selectors with getSecurityRequirementsForOperation for better scope extraction
• Added comprehensive unit tests for the new component

Features

• ✅ Supports ALL security schemes (OAuth2, OpenID Connect, API Key, Bearer, Basic, etc.)
• ✅ Displays scopes/requirements clearly with colored badges
• ✅ Shows AND/OR logic for multiple security requirements
• ✅ Indicates optional authentication
• ✅ Responsive design for mobile devices
• ✅ Non-intrusive UI that complements existing padlock icon

Screenshots

The feature displays security requirements inline:

• OAuth2 scopes shown as badges (e.g., "OAuth2 (read:users, write:users)")
• Multiple auth options shown with OR operator
• Combined requirements shown with + operator
• Optional auth clearly marked

Testing

• Unit tests added for all component scenarios
• Tested with various OpenAPI specs including:
  • OAuth2 with multiple scopes
  • OpenID Connect
  • API Key authentication
  • Bearer/JWT tokens
  • Basic authentication
  • Complex AND/OR combinations
  • Optional security

Breaking Changes

None - feature is backward compatible and doesn't affect existing functionality.

Checklist

• Code follows project style guidelines
• Unit tests added and passing
• No breaking changes
• Feature works with all security scheme types
• Responsive design implemented