perf: optimize main class picker ordering

[Deleted user (ghost)]

Summary

This change reduces unnecessary work in the main class picker by avoiding mutation of caller-owned arrays and by caching the active editor path while reordering recent quick-pick entries.

Why

The picker can get large result sets, and the current code was repeatedly calculating the active file path for each option while also sorting the original array in place. This creates extra work for every launch flow and can make the quick pick noticeably slower when there are many Java main classes.

Changes

• Sort a copied array instead of the caller-owned input array
• Cache the active editor file path once per pick
• Reuse the sorted options rather than re-reading the same data repeatedly

Validation

• npm run compile

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.