[CT-2205] [Feature] Support supply params in dbtRunner.invoke to overwrite flags

[ChenyuLInx]

Feature description

During dbtRunner.invoke, user should be able to supply a configuration set that used for that invocation with the runner.

# this set of params will overwrite attributes that exists on Flags object during initialization of Flags.
# Anything set here will be visible to the structured logs and exposed in jinja context.
params = {"fail_fast": True, 'version_check': False}

# initialize
from dbt.cli.main import dbtRunner  
dbt = dbtRunner()

# this will fail fast, and not check version
dbt.invoke(['run'], params=params)

Requirement

• params will overwrite all other formats of configs(env var, cli specified)(during initialization of Flags)
• Add a structure logging event that include the names of params that got passed in via the params in dbt.invoke
• Add tests for params that we know dbt-server would want to set/overwrite.
  • log_format
  • log_path
  • version_check
  • project_dir
  • profiles_dir
  • profile_name
  • target_dir
• Make sure dbt-server is unblocked

[ChenyuLInx]

By doing it this way, anything set by params will still be visible (name + value) to the structured logs (MainReportArgs), exposed in jinja context (docs) and in the args dict of run_results.json.

Let's confirm that this is acceptable for the intended use case. If it isn't acceptable, we should proceed with this work as currently scoped, and open a new issue to address SensitiveFlags (whose values should be excluded/scrubbed from logging, artifacts, Jinja context).