[Keavon]

Follow-up to #4670. When you hover a node with a wire, it reveals hidden inputs based on a type check that didn't match what the compiler does, so it got things wrong in both directions:

• It assumed every ranked input converts through its element's input_adapter. The preprocessor only puts one in front of inputs registered with a single ranked type. So a Color wire was treated as fitting inputs like Fill's Content, and that fails to compile once connected. Now the editor asks the preprocessor (input_adapter_identifier, the same function it uses itself) which adapter each input gets, and allows only that adapter's conversions.
• It ignored rank promotions, so an item wire going into a list input was rejected even though type resolution handles that case. The promotion rules moved into Promotion::between, and both the compiler and the editor use it now.
• A subgraph import that feeds a Monitor first (like in Path) accepted nearly any type, because Monitor is generic. Nodes that pass their input type through unchanged are now looked through, and what they feed decides what the import accepts.

One example of something this fixes from #4670 is the case of dragging a Vector wire over a Fill or Stroke node which should expand the node to show the Paint parameter. It should work equally for both, as they're both valid. But as of #4670, it only the Fill node works and the Stroke node doesn't expand to offer it, which this followup PR fixes. It also fixes a number of misleading and broken type details across the tooltips, such as the Path node's primary input showing the entire set of all inputs accepted by the Monitor node (essentially all wire types, which the tooltip can't hope to fit on screen).

[TrueDoctor]

I deliberatly choose not to implement this in my pr because dealing with rank promotions is very ugly, I will need time to review this in detail since it touches the compiler and type resolution so you may not merge this on your own

[cubic-dev-ai]

All reported issues were addressed across 6 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[TrueDoctor]

I don't think I'll be able to impartialy judge the code quality at the moment or have time to work on improvements. So if you need merge this to reach some goal, you can do that without risking me holding this against you