Ability to provide CLI params as config

[drjonnicholson]

Idea

Allow all parameters to be defined in the config file, allowing them to be dynamically defined, but still be overridden by the CLI.

Current state

It looks like there are currently options that can only be passed through the CLI. For example, reporters appears to only take configuration from the CLI options.

Example use case

To be able to define reporters in the config, making use of javascript to help define values. Consider a lage.config.js like this where i've put reporter and grouped in the root as an example:

/** @type { import('@lage-run/cli').ConfigOptions } */
module.exports = {
  reporter: process.env.CI ? 'azureDevops' : 'npmLog',
  grouped: true,
  pipeline: {
    build: ['^build'],
    test: ['build'],
    lint: ['build']
  }
}

With the package.json like:

{...,
  "scripts": {...,
    "lint": "lage lint"
  }
}

Then:

• When I call npm run lint on my local I want to see the npmLog reporter
• When I call npm run lint on my Azure DevOps Pipeline ( or manually with CI=true npm run lint) I should see output from the azureDevops reporter
• When I call npm run lint -- --reporter=json anywhere then I expect the report output to be in JSON format