Document @nestia/migrate package with clean JSDoc comments and proper author attribution

[Copilot]

This PR adds comprehensive JSDoc documentation to the entire @nestia/migrate package following clean documentation standards without example code blocks.

What was documented

Core API Classes

• NestiaMigrateApplication - Main class for migrating OpenAPI documents to NestJS/SDK with @author Jeongho Nam - https://github.com/samchon attribution
• Entry points (index.ts, module.ts) with file-level descriptions

Interfaces and Types

Complete documentation for all interfaces in the structures/ directory with proper author tags:

• INestiaMigrateConfig - Configuration options with detailed parameter descriptions
• INestiaMigrateContext - Migration context structure
• INestiaMigrateController - Controller representation
• INestiaMigrateDto - DTO structure definitions
• INestiaMigrateFile - File output structure
• INestiaMigrateProgram - Complete program representation
• INestiaMigrateSchema - Schema hierarchy structure

Code Generation Namespaces

Key programming namespaces with proper author attribution:

• NestiaMigrateNestProgrammer - NestJS application generation
• NestiaMigrateApiProgrammer - API client generation
• NestiaMigrateE2eProgrammer - End-to-end test generation

Utility Functions

Utility namespaces with proper author attribution:

• StringUtil - String manipulation for identifier normalization
• MapUtil - Functional Map operations for memoization patterns
• SetupWizard - Project setup automation

Analysis and Processing

• NestiaMigrateControllerAnalyzer - Route grouping logic with proper attribution
• NestiaMigrateFileArchiver - File system operations with author tag
• TypeLiteralFactory - TypeScript AST generation with attribution

CLI Interface

• migrate.ts - Command-line entry point with file-level documentation
• NestiaMigrateCommander - Main CLI orchestration logic with proper attribution

Documentation Standards Applied

✅ Clean JSDoc formatting with proper descriptions, parameter documentation, and return types
✅ No example code blocks - focused on clear, concise documentation without cluttering examples
✅ Proper author attribution using @author Jeongho Nam - https://github.com/samchon tags on all main classes and interfaces
✅ Public members only - documentation exclusively on public/exported interfaces and functions
✅ Type safety with proper TypeScript integration in documentation

The package now provides clear guidance for developers migrating from OpenAPI/Swagger specifications to NestJS applications or SDK libraries, with proper attribution and clean documentation standards.

Fixes #1348.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Don't documentate on private members.

Also, add @author Samchon tag at the every classes and interfaces (not into the nested members).

Addressed both feedback points in commit 11f21e8:

1. Removed JSDoc from private members: Removed documentation from private data_ property in NestiaMigrateApplication
2. Added @author Samchon tags: Added to all main classes and interfaces including:
   • Main class: NestiaMigrateApplication
   • All structure interfaces: INestiaMigrateConfig, INestiaMigrateContext, etc.
   • Key programming namespaces: NestiaMigrateApiProgrammer, NestiaMigrateE2eProgrammer, etc.
   • Core utility classes and namespaces

The documentation now follows the requested standards with proper @author attribution and no private member documentation.

[Copilot]

Don't need to write example content.

Also, documentate only to the public or exported members. ...

Addressed all requested changes in commit 1cbd8b3:

1. Removed all @example content: Removed example code blocks from all JSDoc comments across the package
2. Documentation only on public/exported members: Verified only public interfaces, classes, and exported functions have documentation
3. Updated @author tags: Changed all @author Samchon to @author Jeongho Nam - https://github.com/samchon on classes, namespaces, and interfaces

The documentation is now clean and follows the specified standards.