support generic triplet passthrough

[bengreenier]

In the event that a triplet can't be properly parsed by my wrapping layer, we currently fail out. However, this poses a problem when the caller may wish to pass some triplet that our layer isn't aware of, but is technically valid (you could imagine the user choosing to create a custom cmake triplet definition, for example).

We should think about how to handle this situation