Firewall: rule_create accepts both integer and string, as port range (e.g. 21-22)

[andreisusanu]

According to the Firewall documentation, rule_create accepts the port parameter as integer or string.

port string (optional) TCP/UDP only. This field can be an integer value specifying a port or a colon separated port range.

The current implementation accepts only integer values, so it cannot create a rule on port range.

Pull request