Unify the iterable and iteration abilities across data structures that should be iterated

[dadepo]

Problem:

Currently the Data structure representing CIDR range is an iterable, while data structure representing IP numbers, although could be iterable is, currently not.

Data structure for CIDR ranges have some sort of stream-like interface for example *take(count?: number) while the data structure representing IP numbers do not, even though they could.

The *take(count?: number) was added ad-hoc fashion. The ReactiveX API has a standard API from which API's like take can be modelled after.

Solution:

• Make data structure representing IP numbers also iterable. Related to Custom nextIPNumber / previousIPNumber [IPv4 / IPv6] #44
• Take a look at the ReactiveX API and borrow (integrate) ideas from there to implement the stream like API for ranges and IP numbers. Related to Implement takeStream, takeStreamUntil and takeStreamWhile (including versions starting from last IP) for IPv4 and IPv6 ranges #30