#129 add community requested source and destination objects

[rvveber]

Pull Request

Related Issue

closes #129

New Behavior

This Merge Request, enables to specify various new Source Entities for the Standard and Extended ACL Rules. It additionally enables to specify the same Entities as a Destination for the Extended ACL Rule. The new selectable entities are all from the IPAM model group:

• IP-Range
• IP-Address
• Aggregate
• Service

I have built in constraints and validation to prevent assigning more than one source/destination. Therefore adding community requested entities, while keeping the functionality the same. No changes to the API, except these newly added fields: source_iprange, source_ipaddress, source_aggregate, source_service and destination_iprange, destination_ipaddress, destination_aggregate, destination_service ...

Contrast to Current Behavior

Previously you could only assign a Prefix as Source and Destination. Now you can assign a Prefix, an IP-Range, an IP-Address, an Aggregate or a Service. ...

Discussion: Benefits and Drawbacks

...

Changes to the Documentation

...

Proposed Release Note Entry

Added requested models for selection as source/destination: IP-Range, IP-Address, Aggregate, Service. ...

Double Check

• [x] I have explained my PR according to the information in the comments or in a linked issue.
• [x] My PR targets the dev branch.