[FEATURE] Please promptly update the intact taco file with a valid signature

### Dear esteemed brother

The signature of the AWS DocumentDB connector file you uploaded has expired. As a result, I am currently using the command -DDisableVerifyConnectorPluginSignature=true forcefully. I believe, as much as you do, that this is not an ideal solution.

I kindly request you to promptly update the signature on the intact taco file. I implore you to save me from this situation.

@birschick-bq

## Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

## Describe the solution you'd like

A clear and concise description of what you want to happen.

## Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

## Additional context

Add any other context or screenshots about the feature request here.

The issue identifies the AWS DocumentDB connector's uploaded taco file and says its signature has expired, but names no repository file, test, or release entry point. Start by locating the connector artifact and the signing process, then verify that the updated artifact has a valid signature and no longer requires the DisableVerifyConnectorPluginSignature workaround.

Written by the indexing model from the issue text.