[json-glib] new port

[talregev]

fix #37698

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

[talregev]

How I add pkg-config executable to meson?
It not detect it correctly on android and windows arm.

[dg0yt]

How I add pkg-config executable to meson?
It not detect it correctly on android and windows arm.

It is correctly setup and used by the build.
Until the package explicitly disables it in order to look for host programs g-ir-scanner and glib-mkenums. There program must be passed to meson via

    ADDITIONAL_BINARIES
        glib-mkenums='${CURRENT_HOST_INSTALLED_DIR}/tools/glib/glib-mkenums'
        g-ir-scanner='${GIR_TOOL_DIR}/tools/gobject-introspection/g-ir-scanner'

after setting up GIR_TOOL_DIR, cf. port gtk and others.

[talregev]

I figure it out. It wasn't problem of detecting pkgconfig. It was problem of cross-build port problem.
With help of @dg0yt I figure out. Thank you.