IGNITE-22435 Add JobTarget interface

[ptupitsyn]

Reduce the number of overloads in IgniteCompute and make the API more readable with new JobTarget interface:

public interface JobTarget {
    static JobTarget node(ClusterNode node);
    static JobTarget anyNode(Collection<ClusterNode> nodes);
    static JobTarget colocated(String tableName, Tuple key);
    static <K> JobTarget colocated(String tableName, K key, Mapper<K> keyMapper);
}

Usage Example

String result = entryNode.compute().execute(
        JobTarget.anyNode(node1, node2),
        JobDescriptor.builder(MyJob.class).units(units()).build(),
        "arg");

JobExecution<String> execution = entryNode.compute().submit(
        JobTarget.colocated("My-table", Tuple.create(Map.of("k", 1))),
        JobDescriptor.builder(MyColocatedJob.class).build());

• Broadcast methods are not affected because of different return type

[isapego]

Should we mention that the collection of nodes is treated as a Set (duplicates are ignored)?

[ptupitsyn]

I don't think this matters with "any node" semantics because we don't explain how a node is picked from the provided collection. There is no guarantee of fairness or randomness on the API level.

[korlov42]

the changes in API module looks good in general. I left a few suggestions on how to improve javadoc though