Remade attestation NONE to work in all cases

[Jeffery-Wasty]

Our original implementation of attestation NONE did work, but as was later shown, not for all cases, and thus a fix was needed. This new NONE enclave provider is a copy of our HGS/VSM enclave provider with attestation validation stripped, and response validation stripped to only what is needed.

SQLServerNoneEnclaveProvider:

• Removed the URL parameter as its never used, removed the catch as a result as IOException is then never thrown
• Removed validation for NONE. After receiving the response, when NONE is selected, the driver does not attempt to verify the response for attestation (enclave details, certificate, etc.) and only computes the shared secret from server's DH public key.
• All that needs to be sent to the server is the enclave type, the challenge, and encrypted ECDH. Subsequently remove anything related to NONCE or attestation URL
• Changed how response is handled. We're only concerned with: total size, session info size and session info, and the server enclave ECDH key, used to validate the enclave session.

EnclavePackageTest

• Added a condition for the second test here (testing a null attestation URL) to not be tested with NONE, as no URL is allowed for NONE, while the test expects a failure.