suppress printing madrat standard config while running start.R

[orichters]

Purpose of this PR

1. Adding a test that I forgot in Fix check if path_gdx_bau is correctly set (NA for no NDC run, not NA for NDC) #1370

2. The first scenario to be started with ./start.R always looks like that:

testOneRegi-Base
   Configuring cfg for testOneRegi-Base
   SLURM option 8 selected: qos=priority nodes=1 tasks-per-node=1 mem=8000
   Run can be started using 0 specified gdx file(s).

Initialize madrat config with default settings..
    regionmapping = regionmappingH12.csv
    extramappings = NULL
    packages = madrat
    globalenv = FALSE
    verbosity = 1
    mainfolder = /p/projects/rd3mod/inputdata
    sourcefolder = NA
    cachefolder = NA
    mappingfolder = NA
    outputfolder = NA
    pucfolder = NA
    tmpfolder = NA
    nolabels = NULL
    forcecache = FALSE
    ignorecache = NULL
    cachecompression = gzip
    hash = xxhash32
    diagnostics = FALSE
    debug = FALSE
    maxLengthLogMessage = 200
..done!

   Writing cfg to file testOneRegi-Base.RData
   If this wasn't --test mode, I would submit testOneRegi-Base.

I don't think that the madrat stuff contains any useful information, given it just reproduces these lines from madrat::initializeConfig().

This is avoided by just calling madrat::getConfig(verbose = FALSE) before starting any scenarios.

Type of change

• Cleanup

Checklist:

• My code follows the coding etiquette
• I performed a self-review of my own code
• I explained my changes within the PR, particularly in hard-to-understand areas
• All automated model tests pass (FAIL 0 in the output of make test)
• I don't think that needs to be mentioned in the changelog.

[0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q]

Forgoing the contraction "don't", while still calling the user a fool, seems like an odd stylistic break. ;)