(#3191) Pass options to Get-WebHeaders

[flcdrg]

Description Of Changes

Pass $options through to Get-WebFileName and Get-WebHeaders

• For remaining headers that don't require special support, check that they aren't 'restricted' before adding them to the Headers collection.

Motivation and Context

Allows being able to set headers via functions like Install-ChocolateyPackage and ensure that those headers are used appropriately.

Testing

Operating Systems Testing

Change Types Made

• Bug fix (non-breaking change).
• Feature / Enhancement (non-breaking change).
• Breaking change (fix or feature that could cause existing functionality to change).
• Documentation changes.
• PowerShell code changes.

Change Checklist

• Requires a change to the documentation.
• Documentation has been updated.
• Tests to cover my changes, have been added.
• All new and existing tests passed?
• PowerShell code changes: PowerShell v2 compatibility checked?

Related Issue

Fixes #3191

[flcdrg]

This may also possibly resolve chocolatey/chocolatey-licensed-issues#372

[pfremy]

I have use for that change too

Or any way to provide implicitely user credentials for some url, in the same principle as is done with "source"