Improve type mismatch detection and reporting

Currently, if Python code passes the wrong number or types of parameters to the host, or returns a result of an unexpected type, `componentize-py` generally reacts by panicking and trapping. That's probably unavoidable in most cases, but it should at least print an informative and actionable diagnostic prior to panicking.

The issue does not name files, tests, or entry points. Begin by locating the parameter and result type-checking paths in componentize-py and review how their current panics are reported. Done means wrong parameter counts or types and unexpected result types produce informative, actionable diagnostics before trapping.

Written by the indexing model from the issue text.