Add a parameter to disable NTLM authentication

On the "Health endpoints parameters" page of the documentation of any AVEVA Adapter, it states that Negotiate (i.e. try Kerberos first and fall back to NTLM if that fails) will be used if a username/password pair and a clientId/clientSecret pair are not specified.

However, NTLM has been deprecated since June 2024 due to various security issues with it, and so, ideally, it should not be used. To help ease the transition away from NTLM authentication, please introduce a parameter to AVEVA Adapters that forbids the AVEVA Adapter from using NTLM authentication at all (i.e. not just for health endpoints, but for all communications).

This parameter's default value should disable NTLM authentication. This way, when the world is done moving away from NTLM authentication, the parameter can just be omitted from the configuration and ignored by the AVEVA Adapter going forward. It also means that administrators of the AVEVA Adapters need to make a conscious choice to allow NTLM authentication and make the AVEVA Adapter less secure, which should help bring the issue of using NTLM authentication to their attention. This is similar to how the default value of the "validateEndpointCertificate" parameter is "true" to make the secure option the default and to ensure that reducing security is a conscious choice. Even though there are ways to disable NTLM authentication for the entire computer, the entire computer might not be ready for this change, and so it helps to have control over the use of NTLM authentication at the program level.