fix: da handling & da status enum

[Senna46]

Overview

Fix some test
Implement enum for DA published data status

// PublishedDataStatus
enum Status {
  // Default value
  STATUS_UNSPECIFIED = 0;
  // Verified
  STATUS_VERIFIED = 1;
  // Rejected
  STATUS_REJECTED = 2;
  // after processing in the msg_server
  STATUS_MSG_SERVER = 3;
  // accept the votes from the validators (after preBlocker)
  STATUS_VOTE_EXTENSION = 4;
  // reported as fraud (after received ChallengeForFraud tx)
  STATUS_CHALLENGE_FOR_FRAUD = 5;
}

Fixed unverified data handling with 4e6e139

[Senna46]

Please review the 3 parts

• IsValidData field of Proof
  This is not used for any handling; there is no need for the validator to send tx that it is Invalid. So, it should be removed.
• ChallengeForFraud collateral
  MsgChallengeForFraud tx can be sent by anyone with collateral coins. This should be handled by the value in PublishedData structure, not param.
  https://github.com/sunriselayer/sunrise/blob/fix/da-test/x/da/keeper/msg_server_challenge_for_fraud.go#L35-L41
• SubmitProof
  MsgSubmitProof tx can be sent by anyone (not validator). I think this differs from the spec; anything that is not from the validator at the time in the EndBlocker should be excluded.

[Senna46]

Changed status names

// PublishedDataStatus
enum Status {
  // Default value
  STATUS_UNSPECIFIED = 0;
  // Verified
  STATUS_VERIFIED = 1;
  // Rejected
  STATUS_REJECTED = 2;
  // After processing in the msg_server
  STATUS_VOTING = 3;
  // Verified the votes from the validators. Challenge can be received (after preBlocker)
  STATUS_CHALLENGE_PERIOD = 4;
  // reported as fraud. SubmitProof tx can be received (after received ChallengeForFraud tx)
  STATUS_CHALLENGING = 5;
}