Zip vs Maven -> Same version different jar files

## Driver version
v2.1.0.30

## Problem description
The jar files in the zip file https://redshift-downloads.s3.amazonaws.com/drivers/jdbc/2.1.0.30/redshift-jdbc42-2.1.0.30.zip and Maven differ. The versions and the number of files are different.

**ZIP file:**
```
aws-java-sdk-core-1.12.731.jar
aws-java-sdk-redshift-1.12.731.jar
aws-java-sdk-redshiftserverless-1.12.731.jar
aws-java-sdk-ssooidc-1.12.731.jar
aws-java-sdk-sts-1.12.731.jar
commons-codec-1.15.jar
commons-logging-1.2.jar
httpclient-4.5.14.jar
httpcore-4.4.16.jar
jackson-annotations-2.16.0.jar
jackson-core-2.16.0.jar
jackson-databind-2.16.0.jar
jackson-dataformat-cbor-2.16.0.jar
joda-time-2.12.7.jar
jsoup-1.16.1.jar
redshift-jdbc42-2.1.0.30.jar
```

**Maven:**
```

com.amazon.redshift
redshift-jdbc42
2.1.0.30

```

```
aws-java-sdk-core-1.12.577.jar
aws-java-sdk-redshift-1.12.577.jar
aws-java-sdk-redshiftserverless-1.12.577.jar
aws-java-sdk-sts-1.12.577.jar
commons-codec-1.15.jar
commons-logging-1.1.3.jar
httpclient-4.5.13.jar
httpcore-4.4.13.jar
ion-java-1.0.2.jar
jackson-annotations-2.12.7.jar
jackson-core-2.12.7.jar
jackson-databind-2.12.7.1.jar
jackson-dataformat-cbor-2.12.6.jar
jmespath-java-1.12.577.jar
joda-time-2.8.1.jar
redshift-jdbc42-2.1.0.30.jar
```

Connecting to Redshift with for example `com.amazon.redshift.plugin.BrowserIdcAuthPlugin` fails when using the Maven artifact due to `aws-java-sdk-ssooidc-1.12.731.jar` is missing. Connecting with the zip file works fine.

Shouldn't these contain the exact same jar files?

Start by comparing the v2.1.0.30 ZIP from the linked S3 URL with the Maven com.amazon.redshift:redshift-jdbc42:2.1.0.30 artifact. Trace how each artifact is assembled and verify why the Maven package lacks aws-java-sdk-ssooidc and uses older dependency versions. Done means both distribution paths contain the intended, matching dependency set and BrowserIdcAuthPlugin connectivity works with Maven.

Written by the indexing model from the issue text.