feat(Jira Trigger Node): Add support for Jira webhook signatures

[pemontto]

Summary

This PR adds support for Jira Webhook signatures based on websub

Effectively we generate a random secret when we create the webhook with the same character set and length as the default Atlassian generated secrets. https://developer.atlassian.com/cloud/jira/platform/webhooks/#secure-admin-webhooks

This PR allows using signature auth, query auth, both, or none.

Review / Merge checklist

• PR title and summary are descriptive. Remember, the title automatically goes into the changelog. Use (no-changelog) otherwise. (conventions)
• [] Docs updated or follow-up ticket created.
• Tests included.

  A bug is not considered fixed, unless a test is added to prevent it from happening again.
  A feature is not complete without tests.

[Joffcom]

@pemontto is this a breaking change?

[pemontto]

It shouldn't be, but there may be edge cases. In my limited simulated updated node testing nothing broke. However thinking of it now, if webhooks don't re-register a guard might be useful to check we actually have a value for webhookData.secret before trying to HMAC and compare on receive.

[Joffcom]

What about the change from options to multioptions or does that not impact anything? We do have another node where we recently introduced the secret option, It could be worth following a similar pattern to that.

@maspio Do you remember which trigger node you added signatures to recently?