SNOW-862760: Add additionalHeader support

[sfc-gh-vkatardjiev]

Overview

SNOW-862760

This adds the ability to send optional headers from the util methods.

External contributors - please answer these questions before submitting a pull request. Thanks!

Please answer these questions before submitting your pull requests. Thanks!

1. What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes #NNNN

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
   • I am adding new logging messages
   • I am modifying authorization mechanisms
   • I am adding new credentials
   • I am modifying OCSP code
   • I am adding a new dependency

3. Please describe how your code solves the related issue.

   Please write a short description of how your code change solves the related issue.

Pre-review checklist

• This change has passed precommit
• I have reviewed code coverage report for my PR in (Sonarqube)

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[sfc-gh-vkatardjiev]

I have read the CLA Document and I hereby sign the CLA

[sfc-gh-igarish]

@sfc-gh-vkatardjiev Do we need any security review here? cc: @sfc-gh-hchaturvedi @sfc-gh-skumbham

[sfc-gh-vkatardjiev]

@sfc-gh-vkatardjiev Do we need any security review here? cc: @sfc-gh-hchaturvedi @sfc-gh-skumbham

None of the headers (or JSON fields) are new from the receiving REST API point of view. All this data can be populated using a curl on any computer connected on the Internet. All snowsight-originated data is validated so that it cannot be spoofed.

Since we're not exposing any new functionality over the network API layer, I don't see a cause for sec review.

[sfc-gh-igarish]

LGTM

[sonarqubemergegate]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information