Fork ID does almost nothing

[nazar-pc]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Description of bug

There is a fork_id field in the chain spec with the following description:

substrate/client/chain-spec/src/chain_spec.rs

Lines 167 to 171 in 4544e6d

	/// Arbitrary string. Nodes will only synchronize with other nodes that have the same value
	/// in their `fork_id`. This can be used in order to segregate nodes in cases when multiple
	/// chains have the same genesis hash.
	#[serde(default = "Default::default", skip_serializing_if = "Option::is_none")]
	fork_id: Option<String>,

However this description is misleading because the only two components aware of this fork_id are beefy-gadget and sc-finality-grandpa. Nothing else in the whole Substrate cares about it even though as a feature it might be helpful at times.

Steps to reproduce

No response

[bkchr]

This will be fixed by this issue: #7746