Editor Usability Issue - non-preferential ports are automatically connected

When dragging off a port and connecting a new node - it doesn't prefer ports of the same type over other ports that can accept the value. Instead it just picks the "first" that works.

Use Case: I have an execution flow data type on nodes - but some nodes accept any basic object type (e.g. debug loggers). Since that object type port was added to the node first, it's the first to respond to the request for a connection when instantiating a new node thus creates an incorrect connection.

Instead - the logic should be something like:

1. Aggregate all ports that could connect to the port we're dragging off from
2. If any are of the same type, pick that first
3. If any are of inherited types, pick those next
4. Pick first of whatever is left over.

No files, tests, or entry points are named. Locate the Unity editor logic that handles dragging from a port and automatically selects a compatible destination, then trace how candidate ports are collected. Done means connections prefer the same type, then inherited types, then the first remaining compatible port, with the described execution-flow and object-port case behaving correctly.