Trap on incorrect callbacktype signature

[carllocos]

Currently, a callback of any type signature can be subscribed via primitive subscribe_interrupt. This is a problem because the callback handler expects registered callbacks to take 5 arguments given that the callback handler pushes 5 stack values prior setting up the call see resolve_event.

On top of my head, we could throw a trap when registering the callback via the subscribe_interrupt primitive. This avoids an out-of-context type mismatch fatal that the VM throws when

[tolauwae]

This is exactly this feature request: #86
And this TODO:

WARDuino/src/WARDuino/CallbackHandler.cpp

Lines 210 to 212 in 6cd2bf6

	// Validate argument count
	// Callback function cannot return a result, should have return type void
	// TODO