Add support for being able to define more than one authentication method per route in the documentation.

[Nicodav28]

Summary
The Scramble library currently supports defining only one authentication method for the entire API. However, many APIs require different authentication methods for different routes. For example, you might have some routes that use Basic Auth and API Key, while others use JWT and API Key.

Request
We would like to request the addition of support for defining multiple authentication methods per route. This would allow more flexible and accurate documentation of APIs where different endpoints require different methods of authentication.

Details
Current Behavior: Scramble allows defining only one authentication method for the entire API. This approach does not accommodate APIs that use various authentication methods for different routes.

Proposed Enhancement

• Implement the ability to specify multiple authentication methods for individual routes.
• Update the documentation generation to reflect the different authentication requirements per route.

Use Cases

• A route requiring Basic Auth and API Key.
• Another route using JWT and API Key.
• Routes with different combinations of authentication methods.

Benefits
Increased Flexibility: Allows accurate representation of APIs with multiple authentication mechanisms.
Improved Documentation: Ensures that API consumers are correctly informed of the required authentication methods for each route.

Additional Information
This enhancement would align with modern API practices and improve the usability of the Scramble library for diverse authentication scenarios.