fix(xo-server): support of cloudbase-init

[MathieuRA]

Description

Related to zammad #30594
See: natevw/fatfs#30 and natevw/fatfs#31
The fatfs library has been forked to implement the createLabel function, which is required otherwise the disk is mounted without label (for windows VMs at least).
Necessary for Cloudbase-Init.

Cloudbase-Init test

• New -> VM.
• Select XCP 8.3.0 XO Team pool
• Select Windows Server 2019 (64-bit) (Cloudbase init) as template
• Check Custom config
• Copy/Past this config in User config (You also can create your own config)

#cloud-config
write_files:
   encoding: b64
   content: NDI=
   path: C:\test
   permissions: '0o466'

• Create the VM
• Wait for the VM to boot (you will need to setup a password for your VM)
• Go to / with cd /
• List with dir
• You should see a file named test. (file created by the cloud-config defined above)
• To read the content of the file: more test (output 42)

You also can create your own template!

• Create a windows server VM
• Install cloudbase-init: https://cloudbase-init.readthedocs.io/en/latest/tutorial.html
• At the end of the installation, check: Run Sysprep
• You can remove the dowloaded file if you want
• edit your cloudbase-init-unattend.conf with at least these 3 things

...
config_drive_vfat=true
...
metadata_services=cloudbaseinit.metadata.services.nocloudservice.NoCloudConfigDriveService
plugins=cloudbaseinit.plugins.common.userdata.UserDataPlugin
...

• Shutdown
• Convert to template

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.

[julien-f]

CI is broken, you likely need to configure ESLint to ignore this package.

[fbeauchamp]

either fix the package or ignore it through an eslint rule
(if the changes are only let/const var and some syntaxic sugar, I would prefer a fix as a separate commits
import package
eslint rule
add new feature

comment resolved

[olivierlambert]

Can I assume it will be available for the next release?

[MathieuRA]

Can I assume it will be available for the next release?

Yes