Add Salesforce symbol indexing

[krzysztofwojt]

Summary:

• Add Apex and Salesforce metadata language support.
• Extract symbols for Apex declarations and common Salesforce metadata entities.
• Cover detection and extraction with synthetic parser tests.

Verification:

• npm test -- tests/parser_types.test.ts tests/salesforce_languages.test.ts
• npm run typecheck
• eslint changed files
• npm run build
• git diff --check

[krzysztofwojt]

Why is this one not a one-liner, like the rest?

[krzysztofwojt]

Why is this added here? Are those changes related to Salesforce?

[Zelys-DFKH]

Thanks for this, Krzysztof. Apex and Salesforce metadata were a real gap here, and the implementation shows it: apex.ts and salesforce_metadata.ts reuse the same helpers the other regex adapters use, the wiring is right, and the test fixtures are real Apex and metadata XML, not toy strings.

On your question about tests/parser_types.test.ts: that file had an exhaustiveness test meant to fail compilation if a Language variant had no test case. Turns out it never actually worked. tsconfig.json only includes src/**/*, so tests/ is never type-checked, and vitest doesn't type-check either. That test was already missing 15 languages with zero CI failures. Your change didn't break anything real. I'll fix or drop that guard myself in a follow-up.

Also saw you already fixed the one-liner style issue in parser.ts yourself. Reads clean now.

One small non-blocking nit: in apex.ts, typeNames.has(name) checks every type name in the file, not just the enclosing class, so a method could get mistagged as a constructor if it shares a name with an unrelated class elsewhere. Fine to leave for later.

Ready to merge from here. Thanks for the careful work, and for flagging what you weren't sure about instead of guessing.

[krzysztofwojt]

Hi @Zelys-DFKH, sorry, this PR was in draft staus, I was actively working on it, and those questions were directed to my Codex :D Code from this PR has some holes, especially for profiles, where whole profiles are getting indexed, which makes no sense. In a moment I'll open a full pull request with a fix for that and tests fully performed ;)

EDIT: no, my bad, I pushed profile-related changes to this PR, so we're fine with that. However, I opened another pull request anyway, with extension of handled salesforce metadata, inluding LWC components.