Model checking: deterministic config resolution and config-based outputs/traces

[younes-io]

• Summary: restore custom model picking for embedded .tla configs and normalize model/trace naming
• Root cause: the new resolver only considered adjacent .cfg files, so custom runs could not select .tla configs
• Fix: add a customPick resolver mode for custom commands and strip .tla from model/trace names
• Tests: npm test

[lemmy]

@younes-io, "restore" implies that there’s a commit that caused the issue. Could you please share the commit? Was it mine? :-)

[younes-io]

You’re right, “restore” was a bad choice of wording.

master never lost .tla-as-config. checkModelCustom on master already lists *.cfg and *.tla.

the "restore" was within this PR, as part of a refactor.

So no “regression commit” on master, and not yours. I've changed the PR's title. Thanks for the tip

[younes-io]

Superseded by #495 (same changes + DCO sign-offs). Closing this PR to avoid duplicate review.