Rename Message struct to IbftMessage

[goran-ethernal]

Description

In order to update libp2p dependencies in Edge, we need to rename the Message struct in messages.proto (which carries the ibft messages like RoundChange, Prepare, etc.), because, libp2p and its pubsub implementation introduced a message.proto which has the struct with the same name in it, so we get a panic over a same name panic:

20
panic: proto: file "messages/proto/messages.proto" has a name conflict over Message
	previously from: "github.com/libp2p/go-libp2p/p2p/transport/webrtc/pb"
	currently from:  "github.com/0xPolygon/go-ibft/messages/proto"

This PR renames the Message struct to IbftMessage, so that we avoid this panic when updating the libp2p dependency.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have added sufficient documentation in code

[sonarqubecloud]

Quality Gate failed

Failed conditions
11.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[Stefan-Ethernal]

As a nitpick, I'd rather call it ConsensusMessage, but it is alright this way as well.

Btw, do we need to rename messages.proto file as well?

P.s. not sure why SonarCloud is complaining, I reviewed the PR from a phone...

[goran-ethernal]

As a nitpick, I'd rather call it ConsensusMessage, but it is alright this way as well.

Btw, do we need to rename messages.proto file as well?

P.s. not sure why SonarCloud is complaining, I reviewed the PR from a phone...

No need to rename messages.proto file. And for the SonarCloud, not sure why it is failing. Even lint got activated for the non affected code.