Make ChatGPT strict mode configurable.

[samchon]

As I've understood that ChatGPT's strict mode is not perfect, and found much better way by giving validation feedback with typia.validate<T>() function, I've changed the ChatGPT strict mode to be configurable, and also changed ChatGPT function calling (or structured output) composition strategy.

From now on, ChatGPT schema also supports the optional properties and dynamic key typed object unless the strict mode configured.

Advised by @AcrylicShrimp

---

This pull request introduces a new strict mode configuration to the ChatGPT schema composer and updates various components to support this feature. The strict mode enforces stricter validation rules, such as requiring all object properties to be mandatory and disallowing additional properties.

Key changes include:

New Features:

• Added a strict configuration option to IChatGptSchema.IConfig to enforce stricter validation rules.
• Updated ChatGptSchemaComposer to use the new strict configuration for validation and transformation. [1] [2] [3] [4]

Validation Enhancements:

• Introduced validateStrict function to enforce strict mode validation rules, ensuring no optional properties and no additional properties are allowed.
• Modified IChatGptSchema.IParameters and related interfaces to reflect the new strict mode constraints. [1] [2] [3]

Schema Updates:

• Updated LlmSchemaV3_1Composer and ChatGptSchemaComposer to handle additionalProperties correctly under strict mode. [1] [2] [3] [4] [5] [6] [7] [8]

Testing:

• Added new test cases to verify the behavior of the strict mode in test_chatgpt_function_calling_additionalProperties, test_chatgpt_function_calling_optional, and test_chatgpt_schema_additionalProperties. [1] [2] [3]

Miscellaneous:

• Bumped the version of the @samchon/openapi package to 2.2.0.

These changes collectively enhance the robustness and flexibility of the schema validation process, especially for use cases requiring strict adherence to predefined schemas.

[samchon]

Test OK