Closed #9763: Treat IP ranges as fully populated

[jeremystretch]

Fixes: #9763

• Add a mark_populated boolean field to the IPRange model
• Replace the add_available_ipaddresses() utility function with annotate_ip_space()
• Introduce the AvailableIPSpace data class to represent unallocated space between two real IP objects
• Extend the get_child_ranges() method the Prefix model to allow passing filters

Note: Calling get_available_ips() on a prefix with mark_utilized=True no longer automatically returns an empty IPSet. This is a deviation from the current behavior that, while not explicitly addressed in the FR, is necessary to ensure the consistent treatment of both prefixes and IP ranges.

[arthanson]

I think there should be a test_filteresets.IPRangeTestCase testing for mark_populated, there should be one for mark_utilized as well, not sure why the test verifier isn't picking up those filter test missing?

There is also the case where you can initially have mark_populated off, then add an IP Address to it, then edit it and make mark_populated True. In this case you can delete the IP Address but you can no longer edit it. Not sure if we want to dis-allow setting the flag if you already have IP addresses created under the range?

[jeremystretch]

There is also the case where you can initially have mark_populated off, then add an IP Address to it, then edit it and make mark_populated True. In this case you can delete the IP Address but you can no longer edit it. Not sure if we want to dis-allow setting the flag if you already have IP addresses created under the range?

IMO it makes sense to disallow editing the IP address, but let's see what feedback we get during the beta.