Enhance FamixTypeScriptImporter to Parse All Object Literal Types and Generate Unique FQNs and fix related issues

[mohbl]

This pull request resolves critical parsing and FQN generation issues in the FamixTypeScriptImporter, enabling it to handle all variations of object literal types—including numeric, string, computed, symbol, and template literal key and ensuring unique fully qualified names (FQNs) for every entity. These changes transform the importer into a robust tool capable of processing any TypeScript project has object types .

1/Object Literal Key Parsing:

• Bug: Importer skipped or crashed on object literals with varied keys (e.g., 1: { method() {} }, [key1]: { method() {} }).
• Fix: Added buildStageMethodMap to map all key types to method positions; updated processStructuredType to process them fully.
• Result: All object literal methods are now modeled correctly.

2/Unique FQN Generation:

• Bug: Methods in object literals had duplicate or missing FQNs (e.g., {file}.method1 instead of {file}.object1.1.method1).
• Fix: Enhanced getFQN to prepend property keys (e.g., 1, keyString, template7) from buildStageMethodMap, ensuring uniqueness.
• Result: Every method gets a distinct FQN like {file}.object1.42.method9[MethodDeclaration]

@fuhrmanator

[fuhrmanator]

Thanks for this contribution!