Add --insecure flag in curl based on request options

[Crocmagnon]

Description

Add the --insecure flag in curl based on request options

Motivation behind this PR?

Closes #554

What type of change is this?

Bug fix

Checklist

• I have added a changelog entry / my PR does not need a new changelog entry. Instructions.
• I have added/updated unit tests. Instructions.
• New and existing unit tests pass locally with my changes. Instructions
• I have self-documented code my changes by adding docstring(s) and comment(s). Instructions
• Current PR does not significantly decrease the code coverage and docstring coverage.
• My code follows the style guidelines of this project.
• I have run ScanAPI locally and manually tested my changes. Instructions.
• I have squashed my commits. Instructions.

Issue

Closes #554

[Crocmagnon]

I didn't find any tests covering curl generation, so I wasn't sure where to start or whether they were necessary.

Please advise :)

I've updated some tests though.

[github-actions]

Thank you for supporting ScanAPI, and congratulations on your first contribution! A project committer will shortly review your contribution.

In the mean time, if you haven't had a chance please skim over the First Pull Request Guide which all pull requests must adhere to.

We hope to see you around!

[camilamaia]

@Crocmagnon, great catch and thanks for the fix!

Indeed, we don't have tests for the template yet, so the ones you added are enough for now. 👍

[camilamaia]

@Crocmagnon Congrats on your first PR merged! 🌟 Thank you very much!

I am going to send you an invite to join the ScanAPI org on GitHub 🚀 We invite everyone that has contributed with a merged PR in any of our repositories. Here you can check our Contributing Guidelines so you can understand better how it works.

Check your email/GitHub notifications to find the invite. If you accept it, you will also be able to clone directly our repositories, without needing to fork them.

Welcome on board and once again, thank you! 🙇‍♀️