Inheritance - a relationship between two types which implies a mechanism for reuse of behaviour
composition - a structural relationship implying whole/part relationship and that the part cannot exist without the whole
aggregation - a structural relationship implying whole/part relationship and that the part can exist without the whole
delegation - a behavioural relationship where a set of behaviours is provided by a different object to the primary receiver of a message.
What is a correct common name for mentioned types of connections?
They are relationships, but are different kinds of relationships - inheritance is a relationship between types, composition and aggregation relationships between objects, and delegation a behavioural relationship. You could have all three kinds present between the same two classes orthogonally.
I can suggest that they all are called 'coupling'
Each one will create (in UML terminology) a «uses» dependency from the package containing the client to the package containing the supplier. When creating dependency graphs between modules in a system, I find it useful to separate simple dependencies and classifier uses (such as the type of an operation, parameter or property); to correctly function you need to import the classifiers used by the elements you depend on, but you don't directly need transitive dependencies or dependencies of classifiers.