compiler parameter order influences enabled flags (release/danger/quick special casing)

[stefantalpalaru]

This is a regression noticed in Nim-1.4.8, using the command line:

-d:release --debugger:native works as expected and generates -g3 -Og -O3
--debugger:native -d:release doesn't generate debugging info, producing only -O3

@xflywind found the PR causing this regression: #18051

An acceptable fix would be to not exclude any flag from conf.globalOptions in here:

Nim/compiler/commands.nim

Lines 489 to 496 in b74b914

	elif cmpIgnoreStyle(key, "release") == 0 or cmpIgnoreStyle(key, "danger") == 0:
	conf.options.excl {optStackTrace, optLineTrace, optLineDir, optOptimizeSize}
	conf.globalOptions.excl {optExcessiveStackTrace, optCDebug}
	conf.options.incl optOptimizeSpeed
	if cmpIgnoreStyle(key, "danger") == 0 or cmpIgnoreStyle(key, "quick") == 0:
	conf.options.excl {optObjCheck, optFieldCheck, optRangeCheck, optBoundsCheck,
	optOverflowCheck, optAssert, optStackTrace, optLineTrace, optLineDir}
	conf.globalOptions.excl {optCDebug}

The only downside is that people with those options in local config files (instead of on the command line) will get unexpected debugging info and verbose stack traces.