Define function input schemas for operations with securitySchemes

[paarthdassani]

What would you like to be added:
An implicit schema should be defined for the function arguments based on the securitySchemes defined in the asyncapi/openapi operation.

Why is this needed:
Different securitySchemes entail different types of inputs from the users.
Eg: basic auth scheme in the openapi spec should translate to "username" and "password" input keys in the function arguments. The runtime should then handle them as defined by the openapi spec.

There could be different such expected inputs for different securitySchemes.
Leaving these to the implementations could affect portability across runtimes, so there should be some behavior defined by the spec to handle these.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.