Check port value when creating firewall rule with icmp protocol

If a firewall rule was created with setting protocol as icmp
and using source/destination port no error was thrown, even though
source/destination port parameters are not used by icmp.

This patch adds a validation method that checks passed parameters
and throws an exception if they are incompatible.

Change-Id: I90a765856896395fcb6e9ddbd888b7bd80480674
Closes-Bug: 1327955
Remove old quantum scripts

This patch removes some old scripts left behind from the quantum days.

Change-Id: I73fb702272e6b93df9ec145da380da88c27259c8
Closes-Bug: #1331664
Revert "ovs-agent: Ensure integration bridge is created"

This reverts commit e5cdad90f97d3a54a493eca19e7a3ff643426de1.

TripleO's multi-node testing shows that this patch caused a failure to receive
tunnel updates, leading to the first node up to have no agent ports, the second
to have one agent port, the third to have 2 agent ports, etc. Needless to say,
this doesn't work all that well :)

Change-Id: Ie90dd4d113a404948dd5debad48065b7db48faa5
Closes-Bug: #1292105
Merge "Revert "ovs-agent: Ensure integration bridge is created""
Merge "Remove old quantum scripts"
Merge "Check port value when creating firewall rule with icmp protocol"