[slang] Add new port (version 10.0)

[timkpaine]

• Changes comply with the maintainer guide.
• The packaged project shows strong association with the chosen port name. Check this box if at least one of the following criteria is met:
  • The project is in Repology: https://repology.org//versions
  • The project is amongst the first web search results for "" or " C++". Include a screenshot of the search engine results in the PR.
  • The port name follows the 'GitHubOrg-GitHubRepo' form or equivalent Owner-Project form.
• Optional dependencies of the build are all controlled by the port. A dependency is controlled if it is declared an unconditional dependency in vcpkg.json, or explicitly disabled through patches or build system arguments such as CMAKE_DISABLE_FIND_PACKAGE_Xxx or VCPKG_LOCK_FIND_PACKAGE
• 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 brief and accurate. See adding-usage for context. Don't add a usage file if the automatically generated usage is correct.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Exactly one version is added in each modified versions file.

[JavierMatosD]

Thanks for the contribution! As we mentioned in #50176, this port installs a CMake package called slang, but the existing shader-slang port already installs a package with the same name.

vcpkg must follow upstream CMake package names exactly, so we can’t rename or override the package name on our side. The maintainer guide only allows unofficial -unofficial configs when upstream provides no CMake package at all, which isn’t the case here.

Because both ports currently provide the same CMake package name, they can’t coexist in the registry. I will open an issue upstream asking how these two libraries are intended to coexist, or whether they would consider providing distinct package names or aliases. Once upstream clarifies their intended naming, we can update the port accordingly.

[JavierMatosD]

I've opened an issue with upstream MikePopoloski/slang#1710

[JavierMatosD]

I'm going to place in draft while we wait on upstream guidance

[timkpaine]

Please link the issue on shader slang as well, thanks for managing this!

[timkpaine]

We've established as slang-verilog on conda: https://github.com/conda-forge/slang-verilog-feedstock