feat: add --debug-level and --category-level flags to apex run @W-18404446@

[WillieRuemmele]

Summary

• Add --debug-level flag to sf apex run (options: NONE, DEBUGONLY, DB, PROFILING, CALLOUT, DETAIL)
• Add --category-level flag for fine-grained per-category control (format: Category=Level, repeatable)
• Flags are mutually exclusive; validates category names and level values
• Input validation with clear error messages for invalid categories/levels

Dependency

Library PR: forcedotcom/salesforcedx-apex#684
This PR requires the @salesforce/apex-node release from the above PR. After that merges and publishes, bump @salesforce/apex-node in package.json to the new version and the CI build will pass.

How to verify

Unit tests (with local library link)

yarn add @salesforce/apex-node@file:../salesforcedx-apex
npx nyc mocha "test/**/*.test.ts"
yarn add @salesforce/apex-node@^9.0.0  # restore

Manual (after library publishes)

# Default behavior (unchanged)
sf apex run -f test.apex

# Set a predefined debug level
sf apex run -f test.apex --debug-level DETAIL

# Set individual category levels
sf apex run -f test.apex --category-level Apex_code=FINEST --category-level Db=FINE

# Verify mutual exclusivity
sf apex run -f test.apex --debug-level DETAIL --category-level Apex_code=FINEST
# ^ should error

# Verify validation
sf apex run -f test.apex --category-level BadCategory=FINEST
# ^ should error with valid category names

@W-18404446@

Test plan

• Existing tests pass unchanged (default behavior preserved)
• --debug-level DETAIL passes debugLevel to executeAnonymous
• --category-level Apex_code=FINEST --category-level Db=FINE passes structured debugCategories
• Invalid format, invalid category, invalid level all throw clear errors
• Manual: verify flag descriptions appear in sf apex run --help
• Manual: verify log output changes with DETAIL vs default on a real org