fix(scanner): prefer non-skipped recipe entries

[gcomneno]

Fixes #494.

bitbake-layers show-recipes can list multiple versions for the same recipe, including skipped entries. The previous parser captured the last repeated entry, so a later skipped version could mark the whole recipe as skipped.

This changes recipe parsing to select the first non-skipped entry for a recipe, falling back to the first entry when all versions are skipped.

Validation:

• npm run compile
• npm run jest -- client/src/__tests__/unit-tests/driver/recipe-parser.test.ts

[deribaucourt]

Thanks again for addressing these issues, this is very helpful!
The parsing is mostly in place, but I had some remarks.

[gcomneno]

I addressed the review comments:

• renamed the unit test file to scanner-unit.test.ts
• renamed the test suite accordingly
• removed the extra empty line in the recipe output fixture
• kept all recipe entries returned by bitbake-layers show-recipes
• reordered entries so a non-skipped/buildable entry appears first when available
• preserved the recipe-wide skipped indicator only when no buildable entry exists

Local validation:

• npm run compile
• npm run lint
• npm run jest -- client/src/tests/unit-tests/driver/scanner-unit.test.ts