feat(xo-stack): implement Query Builder

[OlivierFL]

Description

Important notes:
- The Query Builder modal might not handle all the use cases for now, but as the code handles and uses Complex Matcher queries, it should work when entering complex queries manually in the search field
- The design has been adapted a lot compared to the original version in Figma to handle some use cases, it might change in future versions

Query Builder implementation:

• The filters selected in the modal are translated into a Complex Matcher query used to filter results.
• The query can also be entered directly in the search input, and if possible, it's translated back to filters when opening the modal.

Usage:

• To add filters in the modal, create a schema to use in useQueryBuilderSchema or add new properties to filter on.
• Applying the correct schema type for the related property type enables filtering with the correct operators (e.g. a "number" schema on a "number" field will create <, >, >= etc. operators in the select)
• It's also possible to filter on properties that are not defined in the schema, using the any property filter in the modal (nested properties are also handled, such as boot:firmware:uefi)

Other features:

• Add/Change from And to Or relations
• Add/Convert filters to groups
• Duplicate filters
• Delete filters

Screenshots

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

If you are an external contributor, you can skip this part. Simply create the pull request, and we'll get back to you as soon as possible.

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.