Test FirewallService configuration defaults

* Top-level FirewallService defaults
* FirewallRule defaults
Merge pull request #131 from alphagov/firewall_mvp_tests

[#62380500] Test FirewallService configuration defaults
correction on how to run integration tests
how to run EdgeGateway integration tests
Merge pull request #134 from alphagov/64994818_improve_test_readme

[#64994818] Improve README.md on how to run integration tests
first cut IP range validations

- Fixed the existing 'ip_address' validation. It used to look for only
first four octets.It used to accept IPs like 192.168.100.100/33/33 ,
192.168.100.100/33 etc. Added more strict validation using regex.

- Added a new schema element type 'ip_address_range'. The valid values for
this type are -
* singleIP address
* CIDR
* valid IP range separated by '-'.
* alphabetical values like 'any','internal' and 'external'.
Added validations for above acceptable values.
using IPAddr library for IP/CIDR validations
removed unused regex
checking if ip is ipv4
using IPAddr to compare ips
changing context title to match rest
making idempotency checks easy

@mikepea's suggested that idempotency checks easy if we can accept
dest_ip/ source_ip in  same format as API. This would help us avoid
tranlation back-forth
Merge pull request #132 from alphagov/ip_range_validation

[#64583754] (first cut) IP range validations
firewall source and destination ips are now ranges
nat service: original_ip and translated_ip are ip_address_ranges
tests for ip_address ranges
using ip ranges in nat_service integration tests

Also added test to configure SNAT rule
Merge pull request #135 from alphagov/using_ip_address_ranges

[#64583754] Using Ip address ranges for Firewall and Nat services
fixing build
merge & conflict resolution from master