Feat/handle deployment plans in simnet

[hugocaillard]

Description

• Handle deployment plans in clarinet-sdk (simnet)
• If the deployment plan has been customized with txs other than ContractPublish or EmulatedContractPublish, but the manifest has changed, we generate the new deployment plan and re-apply the custom txs. Instead of prompting the user to ask to if they want to overwrite the changes

Some refactor

• I try to isolate the serialization/de-serialization of the deployment-plan in the clarinet-deployments crates. So that we don't serde-yaml in other crates
• Feature flag some methods that are only used in the cli

Ideas

• In future version we want to extend the feature to clarinet console
• We also need to validate this way of re-apply custom txs and use it for devnet deployment plan handling

[codecov]

Codecov Report

Attention: Patch coverage is 70.47619% with 62 lines in your changes are missing coverage. Please review.

Project coverage is 41.43%. Comparing base (a6d4504) to head (aaca439).

Files	Patch %	Lines
components/clarinet-cli/src/frontend/cli.rs	0.00%	30 Missing ⚠️
components/clarinet-deployments/src/types.rs	62.16%	28 Missing ⚠️
components/clarinet-cli/src/deployments/types.rs	0.00%	2 Missing ⚠️
components/clarinet-cli/src/deployments/mod.rs	0.00%	1 Missing ⚠️
components/clarinet-deployments/src/lib.rs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1360      +/-   ##
===========================================
+ Coverage    41.17%   41.43%   +0.25%     
===========================================
  Files           86       87       +1     
  Lines        31643    31813     +170     
===========================================
+ Hits         13030    13181     +151     
- Misses       18613    18632      +19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[MicaiahReid]

I have one question and one tiny code change, but nothing blocking. Great work!