fix(ui): avoid modal path mapping errors

[gcomneno]

Fixes #441.

The container path mapping error was displayed as a modal VS Code error dialog.

If that dialog cannot be dismissed correctly, it can block the full VS Code UI and force the user to kill the application.

This change keeps the existing error notification and diagnostic details, but avoids using a modal dialog for the container path mapping failure.

Only the path mapping error in BitBakeProjectScanner was changed. Other modal dialogs remain unchanged.

Validation:

• npm run compile
• npm run jest -- client/src/tests/unit-tests/driver/path-mapping-errors.test.ts

[gcomneno]

I addressed the review comments:

• moved the path mapping error test into scanner-unit.test.ts
• removed the separate path-mapping-errors.test.ts file
• removed the non-modal detail usage, since VS Code only renders detail for modal messages
• moved the actionable path mapping explanation into the main error message
• kept the message non-modal by calling showErrorMessage() with only the message argument

Local validation:

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

[deribaucourt]

Rendering is ok.
Thanks again for your awesome contribution!

The next step for me will be to publish a new release with all that's been merged so far.
I think I'll be reaching out to the Yocto maintainers to prioritize the next steps of the backlog.

[gcomneno]

Thanks a lot for the review and merge!

I'm really glad these fixes could help unblock the release path. Looking forward to the next backlog priorities once you have aligned with the Yocto maintainers.