[Performance] Short-circuit framework detection evaluation

[gonzaloriestra]

WHAT is this pull request doing?

This PR optimizes resolveFramework in packages/cli-kit/src/public/node/framework.ts by replacing .reduce() array iteration with short-circuiting .some() and .every() calls for framework.detectors.some and framework.detectors.every.

Why are these changes needed?

Previously, resolveFramework evaluated all detectors for each framework option using .reduce(), which forced reading configuration files from disk and performing regex testing even after a matching detector was found or after a detector failed for every. Using some and every enables short-circuit evaluation, avoiding redundant I/O operations and regex evaluations.

How to test your changes?

CI

---

PR created automatically by Jules for task 3388346819994248700 started by @gonzaloriestra

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.