[glaze] new port

[omarhogni]

• Changes comply with the maintainer guide
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[omarhogni]

@microsoft-github-policy-service agree company="Skaginn 3X ehf."

[omarhogni]

Upstream project requires at least gcc 10 the azure pipelines are built using gcc 9.

/mnt/vcpkg-ci/buildtrees/glaze/src/v1.2.1-af0f635c8a.clean/include/glaze/binary/header.hpp:7:10: fatal error: concepts: No such file or directory
    7 | #include <concepts>
      |          ^~~~~~~~~~
compilation terminated.
ninja: build stopped: subcommand failed.

What is usually done in this situation?

[FrankXie05]

We can wait to merge until a VM update allows us to test this.

Otherwise, we can only temporarily disable the relevant functions as we cannot test it. Sorry for that. 😔

Track: microsoft/azure-pipelines-agent#3834

[dg0yt]

No need to wait.

What is usually done in this situation?

• Tell port users:
  Add a message to the portfile that gcc must be at least <version>.
• Tell vcpkg CI:
  Insert glaze:x64-linux=fail to scripts/ci.baseline.txt

Example: port coroutine.

[omarhogni]

Added the following message and set pipeline failure cases as suggested by @dg0yt

[BillyONeal]

Thanks for the new port!