Smart contract still builds and creates even when creating the transaction type fails and returns a 500

[cheeseandcereal]

• Dragonchain Version: 4.1.0
• Entrypoint: Webserver

Right now, when creating a smart contract, if the transaction type fails to create for an unexpected reason, the webserver will return a 500 and the associated transaction type fails to create, but the smart contract will still be built and added to the chain (making it unusable without the transaction type) regardless.

If the transaction type fails to create, then the smart contract should not be built.

Currently if you run into this bug, you must manually remove the contract that was created.

You can see this unexpected behavior when reproducing #224, but the same issue would likely occur with any unexpected failure to create the transaction type, such as storage errors, which should be handled better.