Demonstrate publishing and consuming build-type-specific header artifacts

We currently publish build-type specific binaries (i.e. debug vs release) but we only publish a single header zip for both. We should create a sample that demonstrates how a user could publish/consume headers that are build-type specific. Optionally, we could also demonstrate consuming these from a custom artifact.

Start by locating the existing sample that publishes build-type-specific binaries and the current single header zip. Add a sample showing how build-type-specific headers are published and consumed; done means the sample demonstrates distinct headers for debug and release, with custom-artifact consumption only if supported.

Written by the indexing model from the issue text.