v1.5.0

This release fixes an issue with rockets in the local provider, which allowed only one rocket to be used when a new message arrived. Before, the system used an environment variable to determine which rocket to call. This caused problems when there were multiple rockets, as the variable would get overwritten. The change now asks the provider for the ID of the specific rocket to be called. For local, the ID is provided in the request, while for others, it is still obtained from the environment variable because, in that case, each rocket will provide its own lambda.