Add flag to roll back package.json transformations after publish

[danpopenko]

Hi,

Before the transformation, package.json looks clean and simple, but afterwards it's a bit messy because changes below the [!start-pkg] marker persist. To keep it clean I currently have to publish locally and avoid pushing, or rely on ci/cd for publishing.

I am wondering if it's possible to add a flag that rolls back all changes after publishing. I can open a PR for this, but I'm not sure it's the direction you want -- from what I can see, you don't currently roll back package.json changes in your workflow, so maybe you prefer the current behavior.

The only issue I can think of is that such a flag would break local usage of the package (e.g., npx link, bin).

Thanks! I really like zile. I can finally use the wevm approach to build libraries with a single cli