jextract: LabeledTuple support!

[ktoso]

We now support passing and returing labelled tuples like (a: Int, b: Stirng) etc.

        var result = MySwiftLibrary.labeledTuple();
        // Access via named accessors
        assertEquals(10, result.x());
        assertEquals(20, result.y());
        // Positional access still works (inherited from Tuple2)
        assertEquals(10, result.$0);
        assertEquals(20, result.$1);

        // The labelled tuple is a subclass of Tuple2
        assertInstanceOf(Tuple2.class, result);
        // And the generic types match positionally as well
        @SuppressWarnings("unused")
        Tuple2<Integer, Integer> check = result;

This is important for being able to quickly port over code from swift to Java using the same libraries as we don't have to special case the labelled tuples and move them over to positional use.

These ad hoc tuple types are printed per method.

They would conflict if you use the same shape twice in a method right now... I'm not seeing much of that use so ignored it for now.

The new tuples inherit from TupleN so Java code can just use them as positional when necessary, also for passing them along to other methods.

The change is large because I also cleaned up type printing, I think printing full qualified type names is good here, better nor risk clashes.

[ktoso]

simpleClassName was crashing on misuse anyway

[ktoso]

we need the method name to form the adhoc types per method

[ktoso]

Double check this one

[ktoso]

TODO: this is pretty horrible, we're getting the field names from the type name...

To make this nicer we need to intreoduce SwiftJavaType that wraps a JavaType since JavaType is just "pure" java types without additional context like this. That's quite a big refactor so we may want to do this but better to do separately...

[ktoso]

potentially more uses here...