fix: Use configured loglevel even when log.condition matches is set

[SystemKeeper]

Right now as soon as we have a matches setting for log.condition, we skip the default loglevel at:

server/lib/private/Log.php

Lines 272 to 283 in 4d00f49

	if (!isset($logCondition['matches'])) {
	$configLogLevel = $this->config->getValue('loglevel', ILogger::WARN);
	if (is_numeric($configLogLevel)) {
	$this->nestingLevel--;
	return min((int)$configLogLevel, ILogger::FATAL);
	}
	// Invalid configuration, warn the user and fall back to default level of WARN
	error_log('Nextcloud configuration: "loglevel" is not a valid integer');
	$this->nestingLevel--;
	return ILogger::WARN;
	}

and if the current logline does not match, we always use WARN:

server/lib/private/Log.php

Lines 303 to 304 in 4d00f49

	$this->nestingLevel--;
	return ILogger::WARN;

• Set the loglevel in config.php to < WARN (e.g. 1 for INFO)
• Define a log.condition => matches that does not match
• Observe that only warnings and above are logged

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[SystemKeeper]

/backport to stable33 please

[SystemKeeper]

/backport to stable32 please

[SystemKeeper]

/backport to stable32