Resolve Azle/dfx dfx.json property name conflicts

[lastmjs]

We have introduced our own custom property names into the dfx.json file, like env, candid_gen, assets, etc. If dfx ever decides to use those names, we will have conflicts. We have thought about this and come up with some possible solutions. We are going to punt on this for now and address it in the future, either when we feel like it or when it becomes a problem.

PR checkbox: What do we do about naming clashes between dfx and Azle in the dfx.json? (We should probably nest azle-specific commands, let's wait on dfinity providing a nice nesting structure? We could always move forward on this now though, which might be a good idea because we're introducing breaking changes now anyway)

• biggest problem is what do we do with clashes between our properties and dfx's
  • nest everything in a custom azle property and have type: azle
  • nest everything in a custom azle property without type: azle
  • handle conflicts, allow extension to choose which fields should be overwritten by the developer and which shouldn't, essentially allowing the extension to rename any fields from dfx.json