composing cps files (or how to handle debug builds created seperately)

Meson doesn't have (by design) a way to generate debug and optimized targets in the same build, instead we would recommend two separate builds for that (we only have out of tree builds, so this is super trivial for us).

The sample has this:
```json
{
"sample-shared": {
"Type": "dylib",
"Requires": [ ":sample-core" ],
"Configurations": {
"Optimized": {
"Location": "@prefix@/lib64/libsample.so.1.2.0"
},
"Debug": {
"Location": "@prefix@/lib64/libsample_d.so.1.2.0"
}
}
}
}
```

It would be impossible for meson to generate this CPS file, however, because of that design decision. For us we would either need a standard way to compose cps files, or to drop the ability to report debug and optimized in a single cps file.