💡Support for experimental container feature flags

[skylerjokiel]

Status	💡 Idea
Target Delivery	TBD

Problem

Developers want to be able to enable experimental features/functionality internal to the container.

Example

We are adding op compression but it's not validated enough that we would turn it on by default for all customers.
#12275

Goal

Developers can enable experimental features internal to fluid.

Proposals

• Extend the AzureClientProps to support flags.

The flags property, as well as the flags themselves, will be optional.

interface ExperimentalFlags {
  exampleFlag1?: boolean,
  exampleFlag2?: "string",
  exampleFlag3?: { foo: string, bar: number} // object
}

interface AzureClient Props {
  readonly connection : AzureRemoteConnectionConfig | AzureLocalConnectionConfig
  readonly logger?: ITelemetryBaseLogger
  readonly experimentalFlags?: ExperimentalFlags
}

Open Questions

• How long do we expect the flags to remain
• What's our support story for flags?
• How do we handle flags that need to span user sessions?
• How does this align with the internal container flags