Move exception logging to separate field

[juliusknorr]

This is a proposal to adjust the log format when exceptions are logged to move them to a separate field in the log json output. The current approach basically leads to the message field being either a string or an object which always bugged me a bit as it is not a unified format. This would also allow easier extraction for some log collection solutions when storing the log details in elastic search for example.

As it is a breaking change on the format we'd need to properly document that in the changelog.

Any oppinions @ChristophWurst @nickvergessen @MorrisJobke @skjnldsv @kesselb

Before:

{
  ...
  "message": {
    "Exception": "Exception",
    "Message": "Unauthorized",
    "Code": 0,
    "Trace": [
      ....
    ],
    "File": "/var/www/html/apps-extra/sharepoint/vendor/vgrem/php-spo/src/Runtime/OData/ODataRequest.php",
    "Line": 51,
    "CustomMessage": "--"
  }
}

After:

{
  ...
  "message": "Unauthorized",
  "exception": {
    "Exception": "Exception",
    "Message": "Unauthorized",
    "Code": 0,
    "Trace": [
      ...
    ],
    "File": "/var/www/html/apps-extra/sharepoint/vendor/vgrem/php-spo/src/Runtime/OData/ODataRequest.php",
    "Line": 51,
    "CustomMessage": "--"
  }
}

[ChristophWurst]

Fine by me :)

[MorrisJobke]

Makes sense 👍

[juliusknorr]

Do we have any place to mention noticable changes for admins in the changelog for example? Maybe something for @jospoortvliet ?

[juliusknorr]

Documentation pr in nextcloud/documentation#6764

[nickvergessen]

Do we have any place to mention noticable changes for admins in the changelog for example?

#26407

[juliusknorr]

Ah also about admins, ok then I'll add to that.