fix: prevent false assignability for types with methods like Map and Set

[puckey]

Summary

• Interfaces like Map and Set have method signatures that aren't included in ObjectType properties, causing isAssignableTo to consider any object with a size property assignable to Map
• This produced wrong conditional type branches (e.g. Immutable<Bar> with T extends Map<infer K, infer V> incorrectly matching when Bar has a size property)
• Track method names on ObjectType, collected in InterfaceAndClassNodeParser
• Check method names in isAssignableTo to reject false structural matches

Test plan

• type-awaited-return-type-break — Immutable<T> with Map/Set branches correctly resolves all properties
• type-self-referencing-method — interfaces with this-returning methods don't cause stack overflow
• All existing tests pass (250/250)

[puckey]

Fixed the formatting in the latest push.

[puckey]

Rebased on next and ran tests.

[arthurfiorette]

@puckey CI is failing

[puckey]

Thanks for the heads up! The failure wasn't the assignability logic — it was the two new test fixtures' tsconfig.json using "moduleResolution": "node", which TS6 now flags as deprecated (TS5107). Since createProgram throws on any getPreEmitDiagnostics output, that deprecation warning failed the type check. Switched both fixtures to "moduleResolution": "bundler" in 0dba093 — passes locally against TS 6.0.2 now.