allow token pass

[ricardo-devis-agullo]

Add Token-Based Authentication for Component Publishing

This PR introduces token-based authentication as an alternative to username/password authentication for publishing components to OpenComponents registries. This enhancement improves security and aligns with modern authentication practices.

Key Changes

Authentication Enhancement:

• Added token parameter support to the publish command CLI interface
• Implemented Bearer token authentication in the registry client (putComponent method)
• Updated credential handling to prioritize token authentication over basic auth
• Enhanced error handling to include token-based authentication failures

Code Quality Improvements:

• Replaced @ts-expect-error with @ts-ignore for better TypeScript compatibility
• Simplified error handling in file watchers and mock plugin registration
• Improved type safety by removing unnecessary type assertions
• Streamlined registry route logic for better maintainability

Dependency Updates:

• Downgraded several dependencies to more stable versions for better compatibility
• Updated development dependencies to maintain consistent tooling versions
• Resolved potential security vulnerabilities in transitive dependencies

Registry API Optimization:

• Refactored component listing endpoint for improved performance
• Simplified metadata filtering logic
• Enhanced component state management and filtering

Usage

The new token authentication can be used alongside existing username/password authentication:

# Using token authentication
oc publish my-component --token "your-bearer-token"

# Using traditional authentication (still supported)
oc publish my-component --username "user" --password "pass"

The authentication system automatically detects the provided credential type and uses the appropriate method for registry communication.

Technical Details

The implementation maintains backward compatibility while adding the new authentication method. Token authentication uses the Authorization: Bearer <token> header format, following OAuth 2.0 standards. The credential resolution logic prioritizes tokens over basic authentication when both are provided, ensuring consistent behavior across different deployment scenarios.