feat(xo-server/api): ability to save all logs for a given call

[julien-f]

Description

The goal of this new feature is to help developers investigate issues by allowing them to easily gather more information.

When enabled, all logs emitted in a given API call are stored in a file (${tmpdir}/xo-api-${date}-${method}.log).

Administrators can use the special _log param to request it:

xo-cli vm.start id=$id _log=json:true

# only keep the log if the call has failed
xo-cli vm.start id=$id _log=failure

Or it can be enabled for all calls to a method in xo-server's configuration:

[api.logs]
'vm.start' = 'failure'

Checklist

• Commit
  • Title follows commit conventions
  • Reference the relevant issue (Fixes #007, See xoa-support#42, See https://...)
  • If bug fix, add Introduced by
• Changelog
  • If visible by XOA users, add changelog entry
  • Update "Packages to release" in CHANGELOG.unreleased.md
• PR
  • If UI changes, add screenshots
  • If not finished or not tested, open as Draft

Review process

This 2-passes review process aims to:

• develop skills of junior reviewers
• limit the workload for senior reviewers
• limit the number of unnecessary changes by the author

1. The author creates a PR.
2. Review process:
   1. The author assigns the junior reviewer.
   2. The junior reviewer conducts their review:
      • Resolves their comments if they are addressed.
      • Adds comments if necessary or approves the PR.
   3. The junior reviewer assigns the senior reviewer.
   4. The senior reviewer conducts their review:
      • If there are no unresolved comments on the PR → merge.
      • Otherwise, we continue with 3.
3. The author responds to comments and/or makes corrections, and we go back to 2.

Notes:

1. The author can request a review at any time, even if the PR is still a Draft.
2. In theory, there should not be more than one reviewer at a time.
3. The author should not make any changes:
   • When a reviewer is assigned.
   • Between the junior and senior reviews.