[api/suggestion] setters should handle `List<Output<T>>`

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

the variadic list setters should handle (List<Output<T>>) instead of having to applyValue().

I think erasure makes this ambiguous? @pawelprazak

    public static Exports stack(Context ctx) {
        var group = new SecurityGroup("web-sg",
                SecurityGroupArgs.builder()
                        .description("Enable HTTP access")
                        .ingress(
                                SecurityGroupIngressArgs.builder()
                                        .protocol("tcp")
                                        .fromPort(80)
                                        .toPort(80)
                                        .cidrBlocks(List.of("0.0.0.0/0" ))
                                        .build()
                        )
                        .build());
        var server = new Instance("web-server",
                InstanceArgs.builder()
                        .ami("ami-6869aa05")
                        .instanceType(Either.ofLeft("t2.micro"))
                        .vpcSecurityGroupIds(group.name().applyValue(name -> List.of(name))) // <=== this
                        .build());
        ctx.export("publicIp", server.publicIp());
        ctx.export("publicDns", server.publicDns());
        return ctx.exports();
    }

Affected area/feature

Start by tracing the variadic list setters used by the vpcSecurityGroupIds example and compare them with applyValue(). Investigate how Java type erasure affects overloads involving List<Output>. Done means the intended setter API and its ambiguity constraints are resolved, with the example no longer requiring applyValue().