(#105) Removes "Hardened" Option, Always Secures

[JPRuskin]

Description Of Changes

We remove the -Hardened option from the Set-SSLSecurity script. Instead, we always pick the options that were in Hardened.

Motivation and Context

There's no reason we shouldn't be recommending that users secure their environment to the extent possible.

If they want to run a less secure environment, they can follow a different guide.

Testing

• [x] Tested locally on Windows Server 2022
• [ ] Automated Testing

I installed QSG locally using the unattend option and a wildcard certificate.

Operating Systems Testing

• Windows Server 2022
• Windows Server 2019

Change Types Made

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

Change Checklist

• [x] 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 v3 compatibility checked?~

Related Issue

Fixes #105

[JPRuskin]

@steviecoaster if you had a minute to eye this over, I think it's ready to merge!