Deployment plan conflicts

[whoabuddy]

Describe the bug

When I run clarinet check I'm prompted to overwrite the deployment plan for simnet.

When I run npm run test on my contracts, the deployment plan is updated again in a different format.

To Reproduce

Steps to reproduce the behavior:

1. Create a new clarinet project and contract
2. Run clarinet check for the project
3. Run npm run test for the project
4. See updated deployment plan

Expected behavior

The deployment plan should be consistent between both tools.

Screenshots

After running the tests:

Changes requested by clarinet check:

Environment (please complete the following information):

• Clarinet version 2.9.0

[hugocaillard]

Related to #1368
Also there could be some quick win there, the new deployment plan strategy shouldn't save empty batches (with: transactions: [])
Will take a look, thanks for reporting @whoabuddy