Feature/init convert

[codespool]

Main feature is introducing a --convert flag to init command. (#111 )
Also handled are #113 and #83 .

Some changes to how init works are introduced:

• all "tasks" now get pushed into the task queue and only executed after all the options are confirmed
• config is also gathered in the global configBuilder, and written as the last step

To test:

• have an existing project cloned to your filesystem (for example dex, or nft from https://github.com/swanky-dapps)
• run swanky init proj_name --convert path_to_existing_project
• it will check for Cargo.toml with workspace members and exclude fields
• it assumes members are contracts, and exclude are extra crates
• you can also specify manually
• when done, you still need to manually adjust import paths in the contracts' Cargo.toml

Note: the converted project is not expected to work out-of-the-box when converted, but should require minimum adjustments.

[shunsukew]

What's the distinction between contractName and moduleName?

[shunsukew]

Not only PSP22 template, but also all other ink!&ask! test templates as well, such as flipper.

[codespool]

oh, a mistake on flipper, but ask! I left out on purpose since I'll remove them in next PR.

[codespool]

What's the distinction between contractName and moduleName?

I noticed on imported contracts that directory name (used for contractName) is often different than [package] name = value. (used now for moduleName)
Typechain used that package name value when creating it's directory structure and file names, so bugs were popping up when contactName was used in constructing the paths for artifacts, tests etc.
I believe that was also the cause of some of the bugs reported.

[shunsukew]

What's the distinction between contractName and moduleName?

I noticed on imported contracts that directory name (used for contractName) is often different than [package] name = value. (used now for moduleName) Typechain used that package name value when creating it's directory structure and file names, so bugs were popping up when contactName was used in constructing the paths for artifacts, tests etc. I believe that was also the cause of some of the bugs reported.

I see,
And when user name contract with Camel case, compile fails, this should be fixed in future PRs #151

[codespool]

Oh, this is actually a bug in this PR, good catch!
When generated, the moduleName should be snake_case.
I'll fix it right away. (that'll close #151 )