Enable http/bearer security in RESTRequest nodes calling APIs defined by OpenAPI V3

OpenAPI V3 updated, from Swagger V2,  the available security schemes that can be defined for a Rest API.  Most notable a securityScheme of type http can use a scheme of 'basic' or 'bearer'. There is also the apiKey type.  It appears that ACE V12 only recognizes the http/basic and apiKey schemes where the RESTRequest node will build the appropriate HTTP Header (or Query) parameters to satisfy these calls, provided that the Username/Password and/or APIKey information is available to the flow via credentials, identity propagation, or set in the LocalEnvironment. 

We are finding that more and more, the APIs that we call from ACE are using bearer authorization with a JWT.  To enable this to work, we need to modify the OpenAPI document to add an apiKey securityScheme definition were we set the key to be a header parameter named 'Authorization' and then set the JWT as the LocalEnvironment.Destination.REST.Request.APIKey value.  While this works, it is inconvenient to have to do this "trick" every time we import an update to the API. 

We would like to have the RESTRequest node fully support the identifying and using a http/bearer securityScheme, if defined in the OpenAPI document.  The value for the bearer token should come from LocalEnvironment.Destination.REST.Request.Bearer.  (or BearerToken).   The node should also examine value of the token and append 'Bearer ' to the beginning if not already present.