Enhance connect Method to Support Authentication Parameters

[Daniel-Boll]

Overview:
This task aims to extend the connect method's functionality within the ScyllaDB driver to support authentication, following the Scylla Rust Driver documentation. The enhancement is crucial for applications requiring secure access to ScyllaDB clusters through authentication credentials.

Detailed Behavior:
The proposed enhancement will modify the connect function to accept multiple types, allowing for an optional authentication object. The authentication object will contain username and password fields for ScyllaDB authentication. This change aims to offer flexibility for establishing authenticated sessions without altering the method's current behavior when authentication details are not provided.

The method should support the following invocations:

1. Connecting with just the keyspace (current behavior):

   const session = await cluster.connect("keyspace");

2. Connecting with keyspace and an authentication object (new behavior):

   const session = await cluster.connect("keyspace", {
     auth: {
       username: "username",
       password: "password",
     },
   });

3. Connecting with an options object that can contain keyspace and authentication details (new behavior):

   const session = await cluster.connect({
     keyspace: "keyspace",
     auth: {
       username: "username",
       password: "password",
     },
   });

Implementation Considerations:

• The function should perform a check to determine the parameter's type(s) passed to the connect method and behave accordingly.
• If introducing multiple types to the connect function proves problematic, the function should be transitioned to use the latter approach (option 3 above), and the initial approach (option 1) should be deprecated with clear communication to the users about this change.
• Proper error handling should be implemented for scenarios where authentication fails or inputs are invalid.

Assignees and Mentions:

• Depending on who has relevant experience or interest, they can be '@' mentioned or assigned to this task.

Impact:

• This task is crucial for users who require secure connections to their ScyllaDB clusters, ensuring that their databases are protected against unauthorized access.

Progress/Updates:

• This issue marks the initiation of this task. Updates on the progress, including discussions, decisions, and implementation phases, will be documented in this thread.