Overall refactor to file structures and types, functions, constants usage

[suhdonghwi]

Key changes

• Keep only plugin definition in src/index.ts, extracted utility functions into dedicated files.
• Abstracted duplicate catalog usability validation logic into get-catalog-protocol-usability.ts.
• Split configuration.ts into multiple files for better separation of concerns.
• Moved constants and types not strictly related to configuration to src/constants.ts and src/types.ts.
• Removed findAllAccessibleGroups and replaced with findDependency.
• Rename some functions (getCatalogDependenciesWithoutProtocol -> getUnusedCatalogDependencies)

Minor changes

• Added typecheck script.
• Added .prettierrc for consistent formatting.
• Use Descriptor types instead of raw string types when possible.

Test result

[parksb]

What do you think about organizing the files by key feature rather than by individual functions? We could split them into four modules:

• configuration: Reading and parsing yarnrc file, resolving catalog descriptors
• inheritance: Resolving inheritance chains, validating inheritance structures
• default: fallbackDefaultAliasGroup, getDefaultAliasGroups, ...
• validation: getGroupValidationLevel, getValidationLevel, ...

We could place these at the same level (it looks like yarn core typically uses a utils directory for this) and have index.ts reference them. This structure might make the code easier to maintain going forward.

[suhdonghwi]

That's a great idea. The only issue is that some functions (e.g. resolveInheritedRange, getValidationLevel) are methods of CatalogConfigurationReader. I'll consider separating those functions so that the Reader class focuses solely on configuration reading.

[suhdonghwi]

I have made changes:

• Now CatalogConfigurationReader only includes config reading, caching, config object validation feature
• Created utils/ directory with default.ts, validation.ts, resolution.ts, functions.ts
  • default.ts: Fallback to default alias group
  • validation.ts: Validate if catalog dependencies are using catalog protocols (if possible)
  • resolution.ts: Resolve catalog dependency & Find all alias groups that contain specific dependency
  • funtions.ts: General utility functions