Fix IResult.ISuccess.value.

[samchon]

This pull request includes a series of changes across multiple files to standardize the usage of the value property instead of data in result objects. The most important changes involve updates to various schema composers, type definitions, and test files.

Schema Composers:

• src/composers/HttpLlmApplicationComposer.ts: Changed result.data to result.value in the return statement.
• src/composers/llm/ChatGptSchemaComposer.ts: Replaced result.data with result.value and updated all references accordingly. [1] [2]
• src/composers/llm/GeminiSchemaComposer.ts: Updated schema assignment from entity.data to entity.value. [1] [2]
• src/composers/llm/LlmParametersComposer.ts: Changed checks and return values from entity.data to entity.value.
• src/composers/llm/LlmSchemaV3Composer.ts: Modified to use result.value instead of result.data throughout the file. [1] [2] [3]
• src/composers/llm/LlmSchemaV3_1Composer.ts: Replaced result.data with result.value and updated all references accordingly. [1] [2] [3] [4] [5] [6] [7]

Type Definitions:

• src/typings/IResult.ts: Changed the ISuccess interface to use value instead of data.

Utility Functions:

• src/utils/internal/OpenApiTypeCheckerBase.ts: Updated the return value from result.data to result.value. [1] [2]

Tests:

• Various test files updated to use result.value instead of result.data in assertions and return values. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

These changes ensure consistency and clarity in how result objects are handled across the codebase.The property data is not proper for the Try<T, E> function;'s return value.