Fix nonDottedPaths handling in cli flow lock generation

[travisp]

Summary

• make wmill generate-metadata --lock-only preserve plain flow step filenames when nonDottedPaths: true
• align flow lock generation with the existing sync pull behavior for flows
• add a regression test covering the non-dotted flow layout

Problem

With nonDottedPaths: true in wmill.yaml, wmill sync pull --yes exports flow steps as plain files like:

• a.ts
• a.lock

But wmill generate-metadata --lock-only rewrites the same flow to:

• a.inline_script.ts
• a.inline_script.lock

and updates flow.yaml to point at those files.

A subsequent wmill sync pull --yes changes the flow back to the plain filenames, so the repo churns back and forth depending on which command ran last.

Fix

This updates flow metadata generation to pass skipInlineScriptSuffix: getNonDottedPaths() to newPathAssigner, matching the behavior already used by flow sync pull.
Since the deprecated wmill flow generate-locks path reuses the same implementation, it benefits from the same fix as well.

Testing

• added a regression test for wmill generate-metadata --lock-only with nonDottedPaths: true
• I personally confirmed the regression test fails without this change and passes with it

Note: this code was supported by gpt 5.4, but manually reviewed and tested.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[travisp]

I have read the CLA Document and I hereby sign the CLA

[rubenfiszel]

thanks a lot!