Normalize pip/conda package-name matching to suppress false MarkupSafe WASM errors

[Copilot]

Pip resolution was treating package names as case-sensitive when checking conda-installed packages, so MarkupSafe requested via pip could be treated as missing even when markupsafe was already present from conda. This produced an incorrect “binary built package not compatible with WASM” warning/error path.

• Solver behavior: normalize names before conda-installed checks

  • Added package-name normalization in solverpip.ts (PEP 503-style comparison semantics: case-insensitive, -_. treated equivalently).
  • Applied normalization when:
    • building the conda-installed package lookup
    • checking top-level pip requirements
    • checking transitive pip dependencies
  • Result: MarkupSafe, markupsafe, and markup_safe now resolve to the same key for conda skip logic.

• Regression coverage

  • Added a focused unit test in unittests/tests/pip/test-solver.ts for:
    • conda has markupsafe
    • pip requests MarkupSafe
    • solver skips pip install and logs as already handled by conda

function normalizePackageName(packageName: string): string {
  return packageName.toLowerCase().replace(/[-_.]+/g, '-');
}

[martinRenou]

LGTM