Feature Request: Configurable Redirect URL after Amazon Redshift JDBC Driver Login

# Feature Request: Configurable Redirect URL after Amazon Redshift JDBC Driver Login

## Summary
Request for a new configuration parameter for the Amazon Redshift JDBC driver. This parameter should accept a URL, which will be used to redirect users upon successful login. If the parameter is not set, the existing behavior—rendering an HTML page with the message "Thank you for using Amazon Redshift! You can now close this window."—should remain unchanged.

## Motivation
The current behavior of rendering a static HTML page post-login is sufficient in many cases, but introducing the ability to redirect to a specified URL can provide more flexibility for different use cases. For instance, this could be helpful in scenarios where organizations want to take users to specific resources or documentation right after login. It also enhances the user experience by integrating with custom web applications more seamlessly.

## Proposed Solution
Add a new configuration parameter, e.g., `redirectUrl`, that accepts a URL. This parameter will be optional. When set, after completing the login process, users will be redirected to the specified URL. If the parameter is not set, retain the current behavior of displaying an HTML page with the message.

### Example Configuration
- **Without `redirectUrl` Parameter**:
`jdbc:redshift://examplecluster.abc123xyz789.us-west-2.redshift.amazonaws.com:5439/dev`

- **With `redirectUrl` Parameter**:
`jdbc:redshift://examplecluster.abc123xyz789.us-west-2.redshift.amazonaws.com:5439/dev?redirectUrl=https://mycompany.com/documentation`

### Example Post-Login Behavior:
- **Without `redirectUrl` Parameter**:
Users see the default HTML page with the message: "Thank you for using Amazon Redshift! You can now close this window."
- **With `redirectUrl` Parameter**:
Users are redirected to `https://mycompany.com/documentation`.

## Benefits

1. **Enhanced Flexibility:** Users have the option to control post-login behavior more precisely.
2. **Improved User Experience:** Directing users to relevant resources without manual intervention.
3. **Custom Integration:** Better support for integrating with custom web applications or organizational flows.

## Potential Drawbacks

1. **Security Considerations:** Redirect URLs might be used for phishing if not properly validated.
2. **Configuration Complexity:** Slight increase in complexity for the JDBC driver configuration.

## Implementation Considerations

1. **Validation:** Ensure the `redirectUrl` is a well-formed URL.
2. **Backward Compatibility:** Ensure the current behavior remains unchanged if `redirectUrl` is not set.
3. **Documentation:** Update the JDBC driver documentation to include usage instructions for the new parameter.

## Request for Feedback

I am proposing this feature and would like feedback from the community and maintainers before submitting a pull request with the suggested feature implemented. Specifically, I am interested in any potential concerns, improvements, or adjustments that could be made to this proposal to ensure it aligns with the project's goals and standards.

Thank you for considering this feature request. I believe it will greatly enhance the flexibility and utility of the Amazon Redshift JDBC driver.

No files or tests are named. Trace the JDBC driver's connection-parameter handling and post-login response, then review how URL validation and redirect safety should work. Done means an optional redirectUrl changes successful-login behavior, the existing HTML response remains the fallback, and documentation and coverage describe both paths.

Written by the indexing model from the issue text.