Whetstone hides original error when using ContributesFragment/ContributesViewModel

[kingsleyadio]

Sometimes, a fragment/viewmodel is incorrectly configured (most notably accessing uninitialized properties). This leads to expected runtime errors. However, because we manage the construction of these entities, such errors get caught and replaced with a Whetstone error that can be very confusing/misleading

We should avoid catching all errors, especially those that have nothing to do with Whetstone. Or at the very least, we should re-propagate such errors to avoid misleading messages