Added support for including a client certificate

[lindsve]

Fixes

This pull request fixes #1971

Description

This PR includes an extension of the WitsmlClient that accepts a X509Certificate client certificate for certificate validation when communicating with a WITSML server.

Due to the added arguments to the WitsmlClient constructor, I've refactored it to accept a WitsmlClientOptions object instead. The previous constructor has been marked as obsolete to move usage over to the new constructor (I removed the Obsolete attribute since it broke the build which seem to be set up to break on warnings)

I've also refactored the WitsmlClient file a bit and extracted some of the content to their own files.

Type of change

• Bugfix
• New feature (non-breaking change which adds functionality)
• Enhancement of existing functionality
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Impacted Areas in Application

• Frontend
• API
• WITSML
• Other (please describe)

Checklist:

Communication

• I have made corresponding changes to the documentation
• PR affects application security

Code quality

• I have self-reviewed my code
• No new warnings are generated

Test coverage

• New code is covered by passing tests

Further comments

[janburak]

• Read issue and PR
• Pulled branch and manually tested
• Verify that PR resolves issue
• Reviewed the code

[lindsve]

@janburak I need you to take a look at it again since I pushed a new commit :) I bumped the nuget package version from 2.7->2.8 since the WitsmlClient constructor has been updated and the certificate support is significant enough to warrant bump in package minor version