feat: plug NodeSecure runtime configuration

[antoine-coulon]

Linked to #2

This PR aims to integrate the @nodesecure/rc lib which would be another way to provide a runtime configuration in addition to the API and CLI options.

More generally it also introduces a way to manage different types of configuration in a transparent way for the @nodesecure/ci runner by providing standardization mechanisms towards a Nsci Configuration.

Consequently here are few semantic choices that can be discussed:

• Nsci configuration becomes the standard interface for a valid configuration in order to run the pipeline
• External configuration becomes the standard format for every external configuration (API, CLI, .nodesecurerc). Each configuration has to implement an adapter than converts the input format of the configuration to the external configuration format.
• Once CLI, API or .nodesecurerc configuration is adapted to the External configuration, the External configuration can be standardized and validated to the Nsci format.

Take for example:

• cli configuration

export type CliConfig = {
  directory: string;
  strategy: Nsci.InputStrategy;
  vulnerabilities: Nsci.Severity;
  warnings: Nsci.Warnings;
  reporters: string | Nsci.ReporterTarget[];
};

• .nodesecurerc configuration, described differently

export interface RC {
  version: string;
   i18n?: i18n.languages;
   strategy?: vuln.Strategy.Kind;
   ci?: {
     reporters?: ("console" | "html")[];
     vulnerabilities?: {
        severity?: "medium" | "high" | "critical" | "all";
     };
     warnings?: CiWarnings | Record<jsxray.kindWithValue | "unsafe-import", CiWarnings>;
   };
}

These two different configurations can be defined by the user upstream the pipeline runner but we want to abstract this
complexity for the runner which should consume a standard format agnostic of configuration changes.

For that, I propose to describe a target standard format for each of these configurations such as:

export type ExternalRuntimeConfiguration = {
  directory: string;
  strategy: Nsci.InputStrategy;
  vulnerabilities: Nsci.Severity;
  warnings: Nsci.Warnings;
  reporters: string | Nsci.ReporterTarget[];
};

Each of the config could then be converted to this format above by implementing a common adapter:

export type ExternalConfigAdapter<T> = {
  adaptToExternalConfig: (config: T) => ExternalRuntimeConfiguration;
};

Once the config is adapted to the ExternalRuntimeConfiguration, its an easy work to sanitize/validate/complete the Nsci standard configuration (check src/config/external/standardize.ts)

[tony-go]

LGTM