typechain-compiler ProjectFiles path option

[shunsukew]

Right now, projectFiles path is configurable only by config.json file as explained in typechain-compiler usage.

export interface Config {
    projectFiles: string[]; // Path to all project files, everystring in glob format
    skipLinting : boolean; // Skip linting of project files
    artifactsPath : string; // Path to artifacts folder, where artifacts will be stored it will save both .contract and .json (contract ABI)
    typechainGeneratedPath : string; // Path to typechain generated folder
}

However, when integrating typechain-compiler to some tools (swanky-cli in our case), we need to compile user-specified contracts only out of all contracts inside swanky-cli's project folder.
(For example, a swanky-cli project sample has flipper and psp22 contracts, and users want to compile flipper only just by passing cli arguments)

To do this, typechain-compiler needs to have a more flexible way of choosing which projects to compile. In addition to config.json file, by taking optional flag like npx typechain-compiler --projectFiles /path/to/project_files