feat!: re-design GetTypeDependencies trait & add GetTypeDependencies derive macro

[makspll]

Summary

Currently the GetTypeDependencies trait struggles with deeply nested container types.

For example HashMap<Result<T,E>,V> would place bounds of GetTypeRegistration on Result which quickly falls apart with non-'static types like Ref and Mut which don't have GetTypeRegistration implementations.

This overhaul introduces the concept of an Underlying type allowing us to have two type trees, the Real types which we want to end up being registered in the registry, and the Facade types which exist purely as trait carriers:

graph TD;
	subgraph facade
	A1[HashMap<.Val<.T>>] --> A2["`Val<.T>`"]
	A2 --> T
	end

	subgraph underlying
    B1[HashMap<.T>] --> B2["`T`"]
    end

Loading

Thanks to that we can make the two assertions confidently:

• I want your REAL types in the script function signature, to be Typed and possible to add to the type registry
• I don't care if your FACADE types are

Also previously, HashMap<T, Val<T>> would not register HashMap<T, T> correctly at all, meaning we now get better dependency coverage!

Migration Guide

• Any types which you implemented GetTypeDependencies for manually, will need to specify an underlying type, for non-generic types this will just be Self, for types which have recursive registrations, this will be Self<T1::Underlying, T2::Underlying...> etc
• You can use the derive macro to make this easier instead