P2P topic IDs should not include Minor/Patch versions of the RuntimeCommitteeProtocol

[ptrus]

P2P topic IDs include RuntimeCommitteeProtocol version:

oasis-core/go/worker/common/p2p/p2p.go

Lines 233 to 235 in 61de25e

	func runtimeIDToTopicID(runtimeID common.Namespace) string {
	return version.RuntimeCommitteeProtocol.String() + "/" + runtimeID.String()
	}

However since we are following SemVer, Minor and Patch version changes to the RuntimeCommitteeProtocol should be backwards compatible therefore also not resulting in a changed topic ID.

[ptrus]

The topics should probably also include chain IDs (or something similar to separate different network meshes).

[kostko]

Yeah so while the messages themselves use the chain domain separation context so they wouldn't be valid, we should probably separate the meshes to avoid needless messages.