[BUGFIX] Add new option to noMatch to not ignore valueDefault

Currently when both noMatch and valueDefault are configured,
the configuration of valueDefault is ignored
because the check for noMatch comes first.

Using both options would be useful though, especially for the L parameter.

Add a new option value "bypassAndApplyDefault" to respect the valueDefault
setting but still bypassing it.

Resolves: #41516

Change-Id: I84dbba11738bb469a17e25e68128c8f0b4c63198