Bump cosmwasm to v1.1, tidy up dependencies, update schema, update CI

[larry0x]

Changes

• Versioning

  • Bump Rust edition to 2021
  • Bump cosmwasm-std to v1.1
  • Bump cw-plus packages to v0.14
  • Bump all contracts and packages in this repo to v0.14 to be consistent with cw-plus

• CI

  • Bump Rust version used in CI to v1.60.0 (was 1.58.1)
  • Bump cosmwasm-vm used in CI to v1.1.0 (was 1.0.0-beta8)

• Dependencies

  • Order all dependencies alphabetically
  • Removed a few unused dependencies
  • Moved a few dependencies that are only used in tests to dev-dependencies

• Schema

  • Replace the derive statement with the new cw_serde decorator, and regenerate schema accordingly:

- #[derive(Serialize, Deserialize, Clone, Debug, PartialEq, JsonSchema)]
- #[serde(rename_all = "snake_case")]
+ #[cw_serde]

• Imports
  • in cw721-base/src/helpers.rs it imports the wrong PhantomData:

- use serde::__private::PhantomData;
+ use std::markers::PhantomData;

I assume this is because someone used editor auto-completion for imports...

Notes

• The most powerful feature provided by cw v1.1, the query response derivation, does not work with cw721-base because it doesn't support query msgs that contain generics. I suggest removing QueryMsg::Extension.
• For types that contain generics, it is necessary to rename them when generating schemas. See this example. That is, you want query_msg.json instead of query_msg_for__cw2891_query_msg.json. The latter won't be picked up by the ts-codegen so is kinda useless.

[webmaster128]

• For dependency version numbers, only keep the first two digits (e.g. v1.x.y --> v1.x). The 3rd digit marks non-breaking changes, so no need to hardcode it. Imo, better leaving it as a wildcard and let Rust compiler determine the most appropriate versions to use.

There can be good reason to do that. If you write "1.2.3" that means 1.2.0-1.2.2 are too low. Those versions might contain a bug you want to prevent in the codebase. Using 1.2 only includes those patch releases. Anyways, probably not important here.

[larry0x]

• For dependency version numbers, only keep the first two digits (e.g. v1.x.y --> v1.x). The 3rd digit marks non-breaking changes, so no need to hardcode it. Imo, better leaving it as a wildcard and let Rust compiler determine the most appropriate versions to use.

There can be good reason to do that. If you write "1.2.3" that means 1.2.0-1.2.2 are too low. Those versions might contain a bug you want to prevent in the codebase. Using 1.2 only includes those patch releases. Anyways, probably not important here.

my understanding is that if i write 1.2, the compiler should automatically choose the latest, which is 1.2.3 in this example, unless there are conflicts making it unable to choose 1.2.3

[webmaster128]

my understanding is that if i write 1.2, the compiler should automatically choose the latest, which is 1.2.3 in this example, unless there are conflicts making it unable to choose 1.2.3

In the average case yes. But you still get lower version if:

• You have 1.2.2, 1.2.1, 1.2.0 in the lockfile already
• Some other crate pins version to e.g. "=1.2.2"

[larry0x]

my understanding is that if i write 1.2, the compiler should automatically choose the latest, which is 1.2.3 in this example, unless there are conflicts making it unable to choose 1.2.3

In the average case yes. But you still get lower version if:

• You have 1.2.2, 1.2.1, 1.2.0 in the lockfile already
• Some other crate pins version to e.g. "=1.2.2"

Good point, will change back

[larry0x]

@webmaster128 I have downgraded the Rust version used in CI to 1.60.0 and use the full version numbers (1.x.y) for dependencies