fix: address build failures in some contracts (#24)

[0xf333]

The build process for some contracts was failing due to issues in certain Cargo.toml files;
Aside from some dependencies paths that needed to be adjusted, there seems to be conflicts with the crate-type setting when using the updated version of the Ink contract compiler. Additionally, the no_main attribute was missing in some contracts.

Description

• Commented out crate-type in Cargo.toml files to resolve conflicts with the updated Ink contract compiler.
• Fixed incorrect Ink dependency path.
• Added the no_main attribute in lib.rs to address missing attributes in some contracts and prevent warning messages.

Impacts

This pull request addresses issue #24

.

[0xf333]

@SkymanOne

[SkymanOne]

I think in this case and better course of action would be to use workspace dependencies like here use-ink/ink#1814

[SkymanOne]

Thanks for taking care of the examples. Left a few comments. I would also use workspace settings in order to maintain all examples with the latest version of ink!
Alternatively, can please also update all contracts to point to the latest ink! minor version?

[0xf333]

Thanks for taking care of the examples. Left a few comments. I would also use workspace settings in order to maintain all examples with the latest version of ink! Alternatively, can please also update all contracts to point to the latest ink! minor version?

Hi @SkymanOne ,
Changes requested have been implemented. However, the cargo-contract compiler currently seems to not support workspace inheritance feature; for more details, you can refer to this link:
use-ink/cargo-contract#1265

I would probably look into the issue #1265 myself and give it a try if I had the opportunity to focus full-time on these.

[SkymanOne]

In this case, no need to bother with the workspace. As long as all dependencies are up to date, we should be good to go