fix: sort remapping candidates to avoid non deterministic output

[Jrigada]

This fixes a non-determinism issue in remapping generation that was causing contracts to produce different compilation hashes across operating systems (see matter-labs/foundry-zksync#1188).

Problem

fs::read_dir returns directory entries in an arbitrary order that varies between platforms (e.g., macOS vs Ubuntu). When multiple remapping candidates exist, they get processed and output in different orders depending on the system, leading to inconsistent compilation hashes for the same contracts.

Fix

Sort remapping candidates before processing to ensure consistent and reproducible output regardless of the underlying filesystem behavior.