meson and cmake install different sets of files

meson installs:

include/json/allocator.h
include/json/assertions.h
include/json/config.h
include/json/forwards.h
include/json/json.h
include/json/json_features.h
include/json/reader.h
include/json/value.h
include/json/version.h
include/json/writer.h
lib/libjsoncpp.a
lib/libjsoncpp.so
lib/libjsoncpp.so.24
libdata/pkgconfig/jsoncpp.pc

cmake installs:

nclude/json/allocator.h
include/json/assertions.h
include/json/config.h
include/json/forwards.h
include/json/json.h
include/json/json_features.h
include/json/reader.h
include/json/value.h
include/json/version.h
include/json/writer.h
lib/cmake/jsoncpp/jsoncppConfig-%%CMAKE_BUILD_TYPE%%.cmake
lib/cmake/jsoncpp/jsoncppConfig.cmake
lib/cmake/jsoncpp/jsoncppConfigVersion.cmake
lib/libjsoncpp.so
lib/libjsoncpp.so.1.9.4
lib/libjsoncpp.so.24
lib/libjsoncpp_static.a
lib/objects-Release/jsoncpp_object/json_reader.cpp.o
lib/objects-Release/jsoncpp_object/json_value.cpp.o
lib/objects-Release/jsoncpp_object/json_writer.cpp.o
libdata/pkgconfig/jsoncpp.pc

Since cmake itself requires jsoncpp we have to use meson to build jsoncpp.
However, some other projects, ex. Microdoft's APSI (https://github.com/microsoft/APSI) look for jsoncpp through cmake files.

Lists of files that cmake and meson install should be identical.

Start by comparing the Meson and CMake installation definitions against the file lists in this issue. Check which installed files are intentional, then align both systems so their installed file sets match and CMake-based dependency discovery continues to work.