Consider adding more type-checking to wasm-tools component link #2591

Inspired by this comment currently the linking phase of wasm-tools component link does type-checks at the item level (e.g. if something is a function or global) and type-checks for globals/tables/memories, but fine-grained type-checks of functions is not yet done. For example if functions are imported with the wrong signature that'll show up as a validation error at the end instead of a linking error. Ideally the linking phase itself would perform these sorts of type-checks and provide an error "faster" to avoid delaying it to a confusing time later on.