fix inconsistent flag names in upgrade proposal command (#7697)

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Author: yihuang

CHANGELOG.md

@@ -40,6 +40,7 @@ Ref: https://keepachangelog.com/en/1.0.0/
 
 * (x/staking) [\#7499](https://github.com/cosmos/cosmos-sdk/pull/7499) `BondStatus` is now a protobuf `enum` instead of an `int32`, and JSON serialized using its protobuf name, so expect names like `BOND_STATUS_UNBONDING` as opposed to `Unbonding`.
 * (x/evidence) [\#7538](https://github.com/cosmos/cosmos-sdk/pull/7538) The ABCI's `Result.Data` field of `MsgSubmitEvidence` does not contain the raw evidence's hash, but the encoded `MsgSubmitEvidenceResponse` struct.
+* (x/upgrade) [#7697](https://github.com/cosmos/cosmos-sdk/pull/7697) Rename flag name "--time" to "--upgrade-time", "--info" to "--upgrade-info", to keep it consistent with help message.
 
 ### API Breaking
 

x/upgrade/client/cli/tx.go

@@ -19,8 +19,8 @@ const (
 	TimeFormat = "2006-01-02T15:04:05Z"
 
 	FlagUpgradeHeight = "upgrade-height"
-	FlagUpgradeTime   = "time"
-	FlagUpgradeInfo   = "info"
+	FlagUpgradeTime   = "upgrade-time"
+	FlagUpgradeInfo   = "upgrade-info"
 )
 
 // GetTxCmd returns the transaction commands for this module