message: Remove submessages from Ibc Responses as well
diff: @@ -9,7 +9,7 @@ use std::fmt;
  use crate::binary::Binary;
  use crate::coins::Coin;
  -use crate::results::{Attribute, CosmosMsg, Empty, SubMsg};
  +use crate::results::{Attribute, Empty, SubMsg};
  use crate::timestamp::Timestamp;
  /// These are messages in the IBC lifecycle. Only usable by IBC-enabled contracts
  @@ -202,14 +202,11 @@ pub struct IbcBasicResponse<T = Empty>
  where
  T: Clone + fmt::Debug + PartialEq + JsonSchema,
  {
  - /// Optional list of "subcalls" to make. These will be executed in order
  - /// (and this contract's subcall_response entry point invoked)
  - /// *before* any of the "fire and forget" messages get executed.
  - pub submessages: Vec<SubMsg<T>>,
  - /// After any submessages are processed, these are all dispatched in the host blockchain.
  - /// If they all succeed, then the transaction is committed. If any fail, then the transaction
  - /// and any local contract state changes are reverted.
  - pub messages: Vec<CosmosMsg<T>>,
  + /// Optional list of messages to pass. These will be executed in order.
  + /// If the ReplyOn member is set, they will invoke this contract's `reply` entry point
  + /// after execution. Otherwise, they act like "fire and forget".
  + /// Use `call` or `msg.into()` to create messages with the older "fire and forget" semantics.
  + pub messages: Vec<SubMsg<T>>,
  /// The attributes that will be emitted as part of a "wasm" event
  pub attributes: Vec<Attribute>,
  }
  @@ -220,7 +217,6 @@ where
  {
  fn default() -> Self {
  IbcBasicResponse {
  - submessages: vec![],
  messages: vec![],
  attributes: vec![],
  }
  @@ -240,14 +236,11 @@ where
  /// The bytes we return to the contract that sent the packet.
  /// This may represent a success or error of exection
  pub acknowledgement: Binary,
  - /// Optional list of "subcalls" to make. These will be executed in order
  - /// (and this contract's subcall_response entry point invoked)
  - /// *before* any of the "fire and forget" messages get executed.
  - pub submessages: Vec<SubMsg<T>>,
  - /// After any submessages are processed, these are all dispatched in the host blockchain.
  - /// If they all succeed, then the transaction is committed. If any fail, then the transaction
  - /// and any local contract state changes are reverted.
  - pub messages: Vec<CosmosMsg<T>>,
  + /// Optional list of messages to pass. These will be executed in order.
  + /// If the ReplyOn member is set, they will invoke this contract's `reply` entry point
  + /// after execution. Otherwise, they act like "fire and forget".
  + /// Use `call` or `msg.into()` to create messages with the older "fire and forget" semantics.
  + pub messages: Vec<SubMsg<T>>,
  /// The attributes that will be emitted as part of a "wasm" event
  pub attributes: Vec<Attribute>,
  }
  @@ -259,7 +252,6 @@ where
  fn default() -> Self {
  IbcReceiveResponse {
  acknowledgement: Binary(vec![]),
  - submessages: vec![],
  messages: vec![],
  attributes: vec![],
  }
  