feat: adds file --output and --sbomOutput flags to specify custom file paths

[v3nant]

Custom Output Paths

Summary
Enabled hd scan eol to write reports and SBOMs to caller-defined destinations and improved related UX.

What changed

• Added --output and --sbomOutput flags with validation ensuring they pair with --save / --saveSbom.

• Updated scan workflow to pass custom paths into the file service, adjust display hints, and emit warnings when outputs are skipped.

• Refactored file service to resolve absolute targets, enforce directory existence, and standardize JSON write error handling.

• Expanded E2E and unit coverage around new flags, error cases, and cleanup helpers; documented the workflow in README examples.

• Prevented the cleanup spinner from running when commands fail, so warning messages remain visible.

[KLongmuirHD]

➜  cli git:(feat/output-flags) npm run dev -- --dir=/Users/klongmuir/HeroDevs/signals-playground --save --output=/Users/klongmuir/HeroDevs/nes/eol-api --saveSbom --sbomOutput=/Users/klongmuir/HeroDevs/nes/eol-report-card/banana.sbom.json

> @herodevs/cli@2.0.0-beta.10 dev
> npm run build && ./bin/dev.js --dir=/Users/klongmuir/HeroDevs/signals-playground --save --output=/Users/klongmuir/HeroDevs/nes/eol-api --saveSbom --sbomOutput=/Users/klongmuir/HeroDevs/nes/eol-report-card/banana.sbom.json


> @herodevs/cli@2.0.0-beta.10 build
> shx rm -rf dist && tsc -b

✔ Generated SBOM
SBOM saved to /Users/klongmuir/HeroDevs/nes/eol-report-card/banana.sbom.json
✔ SBOM trimmed
✔ Scan completed
Error: Failed to save eol-api: EISDIR: illegal operation on a directory, open '/Users/klongmuir/HeroDevs/nes/eol-api'
    at Object.error (/Users/klongmuir/HeroDevs/nes/cli/node_modules/@oclif/core/lib/errors/error.js:44:15)
    at ScanEol.error (/Users/klongmuir/HeroDevs/nes/cli/node_modules/@oclif/core/lib/command.js:210:23)
    at ScanEol.saveReport (file:///Users/klongmuir/HeroDevs/nes/cli/dist/commands/scan/eol.js:206:18)
    at ScanEol.run (file:///Users/klongmuir/HeroDevs/nes/cli/dist/commands/scan/eol.js:144:37)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async ScanEol._run (/Users/klongmuir/HeroDevs/nes/cli/node_modules/@oclif/core/lib/command.js:181:22)
    at async Config.runCommand (/Users/klongmuir/HeroDevs/nes/cli/node_modules/@oclif/core/lib/config/config.js:456:25)
    at async run (/Users/klongmuir/HeroDevs/nes/cli/node_modules/@oclif/core/lib/main.js:97:16)
    at async main (file:///Users/klongmuir/HeroDevs/nes/cli/bin/main.js:20:5)
    at async file:///Users/klongmuir/HeroDevs/nes/cli/bin/dev.js:6:3

issue: if I don't provide a file name in the output path, the CLI errors. If the path the user provides is just a directory, and doesn't give a custom filename, we should save with the default file name, to that path. So in this example, I would expect herodevs.report.json to be saved to my eol-api directory. Apply to both new flags.