feat: Allow to change SSL verify in HTTP Node

[DavideDelbianco]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

This PR completes the closed #17216 adding the missing FrontEnd part
When adding a HTTP Node to your workflow the backend will send the expected default state of the switch, based on the ENV variable HTTP_REQUEST_NODE_SSL_VERIFY

Screenshots

Before	After

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[QuantumGhost]

I recommend adding a warning tooltip to the "VERIFY SSL CERTIFICATE" toggle to inform users about the security implications of disabling SSL verification. The tooltip should clearly indicate that this option should only be disabled in exceptional circumstances (e.g., development/testing environments) and that disabling it in production environments poses significant security risks by making the connection vulnerable to man-in-the-middle attacks.

[DavideDelbianco]

Something like that?

[crazywoola]

Something like that?

@DavideDelbianco Please proceed with this tooltip.