Handle fatal log level in occ log:manage

[phil-davis]

Description

Add the "fatal" log level to the list of log levels that the occ log:manage command knows about.
And similar for LoggingHelper.

Related Issue

#28679

Motivation and Context

Make occ log:manage work with the same log levels as available in the UI.

How Has This Been Tested?

1. Set log level to Fatal in the UI.
2. occ log:manage and confirm it produces good output
3. Use occ log:manage to change to another log level - make sure the UI shows the new level.
4. Use occ log:manage to change to fatal log level - make sure the UI shows the fatal level.

Make some UI tests that set the logging level to "fatal" and confirm that they run.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[PVince81]

This is the original PR: #18369

There is no mention of purposefully omitting "fatal", it was likely an oversight.

[PVince81]

👍

[phil-davis]

Backport stable10 #28683

[mmattel]

@phil-davis @PVince81

'set the log level [debug, info, warning, error, fatal]' is not updated in
documentation https://github.com/owncloud/documentation/blob/94ffcbc41d85789a61a5fe5eda0cc717b8684f62/admin_manual/configuration/server/occ_command.rst

log:manage sets your logging backend, log level, and timezone. The defaults are owncloud, Warning, and UTC. Available options are:

--backend [owncloud, syslog, errorlog]
--level [debug, info, warning, error]

[phil-davis]

Doc update owncloud-archive/documentation#3310

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.