Support configs to be passed in SchemaRegistryProvider to support google managed schema registry client auth

### Feature Description

**What the feature achieves:**
Support configs to be passed in SchemaRegistryProvider for CachedSchemaRegistryClient constructor initialization.

**Why this feature is needed:**
GCP Schema registry is compatible with confluent but it requires additional config for auth. Existing SchemaRegistryProvider have CachedSchemaRegistryClient with null config in constructor.

### User Experience

**How users will use this feature:**
- GCP users can pass properties in typedProperties for SchemaRegistryProvider with allowed prefixes to support auth.

### Hudi RFC Requirements

**RFC PR link:** (if applicable)

**Why RFC is/isn't needed:**
- Does this change public interfaces/APIs? - No
- Does this change storage format? - No
- Justification: We can support auth for gcp schema registry clients as well by this change.

Start by locating SchemaRegistryProvider and its CachedSchemaRegistryClient constructor initialization, then trace how typedProperties are read and filtered by allowed prefixes. Confirm the required Google-managed schema registry authentication properties from the surrounding integration and verify that they reach the client configuration without changing public interfaces.

Written by the indexing model from the issue text.