fix(@xen-orchestra/rest-api): fix null values not displayed as nullable

[MathieuRA]

Description

This option is required to not loose the nullable option on null properties when using dynamic type.
E.g.

type WithFoo <T> = T {foo: string} 

WithFoo<{bar: null | string}> 

Will return this openapi spec:

type: object,
properties: {
   bar: {
     type: string
   },
   foo: {
     type: string
   }
}

With this option enabled, it will generate a spec like:

type: object,
properties: {
   bar: {
     type: string,
     nullable: true
   },
   foo: {
     type: string
   }
}

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.

[fbeauchamp]

comment error, please ignore