[portable-file-dialogs] Add new port

[myd7349]

• 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.

[JonLiu1993]

@myd7349, Thanks for your PR, I see that the upstream code provides a CMakeLists file, why not install the CMakeLists file?

[JonLiu1993]

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

[myd7349]

@myd7349, Thanks for your PR, I see that the upstream code provides a CMakeLists file, why not install the CMakeLists file?

Hi @JonLiu1993 Thanks for your review.

Due to the lack of an "install" target in the CMakeLists.txt provided by the upstream repository, it is not possible to install the library using vcpkg_cmake_install. Currently, there is a PR that adds the install target for this library, but it has not been merged yet.

In light of this, considering that the library consists of a single header file, this approach has been adopted for installation.