feat(manager/gradle): reimplement parser using tree-based approach

[Churro]

Changes

• Re-implementation based on https://github.com/zharinov/good-enough-parser
• Parsing capabilites are on par with the existing parser
• Handler methods that process matches are functionally identical with the existing parser
  • For most parts of handler.ts, control and data flow were taken 1:1 from the existing implementation
  • Nesting was reduced, i.e., instead of doing if (dep) { ... } -> if (!dep) { return ctx; }
• Tests were only adapted at points where unavoidable to demonstrate parity

Tokenizer, no longer needed types, etc of the existing parser are still there. I'd intend to do a follow-up cleaning PR.

apply from

The switch to the new parsing lib changed how apply from is implemented too:

• Until now, files were read async and recursively passed to parseGradle (more context here)
• The query interface of the new parser returns strictly Ctx, which means no async calls possible. I'm aware of 2 alternatives:
  • Use fs.readFileSync() - disapproved here: feat(manager/gradle): add support for apply from statements #16030
  • Use getFileContentMap() to load Gradle files upfront. This is used here
    • Pros: apply from respects fileMatch and ignorePaths now
    • Cons: Higher (but acceptable?) heap mem usage, examples:
      • Signal Android app: 34 Gradle files, 75 kB in total
      • react-native: 9 Gradle files, 71 kB in total
      • elasticsearch: 429 Gradle files, 947 kB in total

Context

#18484

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[PhilipAbed]

looks good overall, will this PR solve #17657?

[Churro]

@PhilipAbed, this PR will not yet solve #17657 but a subsequent one. Implementation + tests for it are already ready and can be viewed in #18484

[viceice]

otherwise LGTM

[viceice]

🤷‍♂️

[renovate-release]

🎉 This PR is included in version 34.26.0 🎉

The release is available on:

• GitHub release
• 34.26.0

Your semantic-release bot 📦🚀