Always set the CLIENT_LOCAL_FILES flag. Fixes #853

If the AllowLoadLocalInfile=True connection string option is specified, then always pass the CLIENT_LOCAL_FILES flag to the server, regardless of whether it was set in the initial handshake packet.

This works around a problem where the Azure Database for MySQL/MariaDB proxy may not specify that flag, but the backend server supports it.

Author: bgrainger

src/MySqlConnector/Protocol/Payloads/HandshakeResponse41Payload.cs

@@ -20,7 +20,7 @@ private static ByteBufferWriter CreateCapabilitiesPayload(ProtocolCapabilities s
 				(serverCapabilities & ProtocolCapabilities.PluginAuthLengthEncodedClientData) |
 				ProtocolCapabilities.MultiStatements |
 				ProtocolCapabilities.MultiResults |
-				(cs.AllowLoadLocalInfile ? (serverCapabilities & ProtocolCapabilities.LocalFiles) : 0) |
+				(cs.AllowLoadLocalInfile ? ProtocolCapabilities.LocalFiles : 0) |
 				(string.IsNullOrWhiteSpace(cs.Database) ? 0 : ProtocolCapabilities.ConnectWithDatabase) |
 				(cs.UseAffectedRows ? 0 : ProtocolCapabilities.FoundRows) |
 				(useCompression ? ProtocolCapabilities.Compress : ProtocolCapabilities.None) |