Custom API widget allow-insecure not respected for newRequest

[furtivespy]

Description

When making a secondary API call with a newRequest in a custom-api widget, the value for the widget's allow-insecure setting is not used. That means that an initial call will work for a self-signed server, but will not on a secondary call.

Logs:

ERROR Could not fetch response within custom API template error="Get \"https://192.168.0.150...\": tls: failed to verify certificate: x509: certificate signed by unknown authority"