Promote FunctionParameter.type to TPowerQueryType; fix isCompatible left-side Any/AnyUnion and two related bugs

[JordanBoltonMN]

Summary

Promotes FunctionParameter.type from TypeKind | undefined to the full TPowerQueryType | undefined, and fixes a family of latent bugs in isCompatible around bare Any/AnyUnion on the left-hand side (plus two additional pre-existing bugs discovered nearby during review).

Motivation

isValidInvocation/typeCheckInvocation previously collapsed isCompatible's three-state result (true / false / undefined) incorrectly in several branches, and FunctionParameter could only express a primitive TypeKind, losing nullability/extended-type fidelity (e.g. list, record, table parameter types). This blocked a downstream ask from powerquery-language-services for richer parameter type information in hover/signature-help/diagnostics.

Changes

• isCompatible.ts: Added explicit handling for Any/AnyUnion on the left-hand side.
  • Bare Any on the left → undefined (indeterminate) in general — it represents absence of constraint, not proof of compatibility, so it must not short-circuit to true. Two deterministic exceptions are special-cased: right = AnyNonNull → true (a non-nullable Any trivially satisfies "anything but null"), right = Null → false (bare Any can never be exactly null).
  • AnyUnion on the left → new isAnyUnionCompatibleWith helper using all-semantics (false on any definite mismatch, undefined if any member is indeterminate, else true).
  • Renamed isCompatibleWithAnyUnion → isRightAnyUnionCompatible for clarity (unioned type on the right retains existing some-semantics), and fixed a pre-existing bug: it previously used a truthy check that collapsed an indeterminate member to a hard false; it now correctly returns undefined when no member is definitely true but at least one is indeterminate.
  • Deleted isCompatibleWithFunctionParameter (superseded by direct isCompatible calls in typeCheckInvocation).
  • Fixed a pre-existing bug in isDefinedListTypeCompatibleWithListType: it used Boolean(array.find(v => v === undefined || v === false)), which is unconditionally false regardless of input (Array.find returns undefined on "not found," and Boolean of undefined/false is always false). Replaced with .every(v => v === true), so this compatibility check — previously non-functional — now actually reports true when every list item type matches.
• type.ts: FunctionParameter.type is now TPowerQueryType | undefined; isNullable is removed and folded into type — an optional parameter's implied nullability is now baked into the constructed type (optional implies nullable).
• typeUtils.ts: inspectAstParameter/inspectContextParameter updated to construct full types per the above. Removed isValidInvocation — dead code with zero callers in this repo and in powerquery-language-services (superseded entirely by typeCheckInvocation).
• typeCheck.ts: CheckedInvocation gained an indeterminate: ReadonlyArray<number> bucket. typeCheckInvocation rewritten to explicitly bucket each argument index into valid/invalid/missing/indeterminate based on isCompatible's tri-state result, rather than conflating them via isCompatibleWithFunctionParameter. Also made two pre-existing truthiness collapses explicit (=== true) now that isCompatible can return undefined.
• nameOf.ts / isEqualType.ts: Updated to work against the new FunctionParameter.type shape.
• Test suites updated across isCompatible.test.ts, isEqualType.test.ts, nameOf.test.ts, typeCheck.test.ts, typeUtils.test.ts to match, including new coverage for the Any/AnyUnion-on-the-left fix and both additional bug fixes above.

Compatibility note

CheckedInvocation's new indeterminate field and FunctionParameter's shape change are public API surface changes. powerquery-language-services pins a specific parser version, so this is non-breaking until it explicitly bumps its dependency (tracked separately).

Testing

• npm run build — clean
• npm run lint — clean
• npm test — 705 passing, 0 failing, 1 pending