Feature/v2 http-plugin dangerous settings / disable ssl verification - issue #518

[RickeyWard]

Since the HTTP plugin uses Reqwest under the hood, this adds the ability to set Reqwest client builder flags for danger_accept_invalid_certs and danger_accept_invalid_hostnames

Its on the roadmap as a proposal via #518

I'm uncertain how versioning works with the plugins-workspace monorepo, but I bumped the version of the http plugin.

I put this behind a feature flag for security reasons.

I attempted to follow existing conventions as closely as possible.

API changes allow for

await response = fetch("https://expired.badssl.com", 
                                          { danger: { acceptInvalidCerts: true, acceptInvalidHostnames: true } }
                             );

[FabianLars]

I'm uncertain how versioning works with the plugins-workspace monorepo, but I bumped the version of the http plugin.

No manual version bumps, only change files like https://github.com/tauri-apps/plugins-workspace/blob/10ce3537b460a1e72e8c9063f6ad910a24140664/.changes/persist-cookies.md

[github-actions]

Package Changes Through 6c58554

There are 2 changes which include http with minor, http-js with minor

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
api-example	2.0.11	2.0.12
api-example-js	2.0.8	2.0.9
http	2.2.0	2.3.0
http-js	2.2.0	2.3.0

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[tweidinger]

LGTM