Expand conditional types in hover popup

[FnControlOption]

[Techatrix]

const foo = if (true) 1 else true;

const bar = if (true)
    .{ foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo }
else
    .{ foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo, foo };

Hovering over bar will cause ZLS to consume huge amounts of memory. Not sure when it stops but it's at least 10GB.

[Techatrix]

const a = if (true) 1 else true;
const b = if (true) false else 0;
const c = if (true) .{ a, b } else .{ b, a };
const d = if (true) .{ a, c } else .{ b, c };
const e = if (true) .{ c, d } else .{ d, c };
const f = if (true) .{ d, e } else .{ e, d };
const g = if (true) .{ e, f } else .{ f, e };
const h = if (true) .{ f, g } else .{ g, f };

Hovering over h will hang. Limiting the total number of combinations that will be analyzed should be a simple solution to this.

[Techatrix]

There shouldn't be a config option for this. We can pick a limit that is high enough to not affect users with real code but low enough to prevent hand crafted examples like mine. There is no point in giving users choices they shouldn't need to make.

For testing, the option in analysis.zig can remain with a default value. The specific tests can then override it if needed.