Possible extension: new message Identify_Consumer_Range and Identify_Producer_Range

[dpharris]

Identify Event Range ( event-range )

This would, for example, let fast clocks determine consumers for its time-events with less traffic.

Nodes may need to fall back to previous methods, it it does not achieve good results with this method:

• enumerate nodes' IDs and then query each node for eventids with Identify_Events_Addressed message.
  This may require a 'rolling' enumerate of nodeIDs, if memory is limited.
• enumerate all eventids globally with Identify_Events_Global This method can lead to significant bus traffic, sufficient to cause network problems.

[bobjacobsen]

For some discussion, please see https://groups.io/g/openlcb/topic/97979505#14916