azure_rm_securitygroup: allow string priority

[xkrt]

SUMMARY

Due to #9362 Ansible jinja filters fails to convert strings to integers in complex objects scenario and azure_rm_securitygroup do not follow best practices for converting strings to integers in arguments where possible (descibed here #17992 (comment)), so if pass string value like '123' to priority argument - I get an error:

... 'priority': '123' - Rule priority attribute must be an integer.

I fix that by parsing priority if it have type string.
Plus I fix false changed: True for scenario where source_port_range or destination_port_range just single ports, compare_rules function compared strings with integers, which always led to false changed.

Tested with Ansible 2.3.0rc3.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

azure_rm_securitygroup

ANSIBLE VERSION

ansible 2.3.0.0
  config file = /vagrant/ansible/ansible.cfg
  configured module search path = Default w/o overrides
  python version = 2.7.12 (default, Nov 19 2016, 06:48:10) [GCC 5.4.0 20160609]

[xkrt]

@chouseknecht @nitzmahone plz review

[xkrt]

@nitzmahone what committer_review label means? can't find it at https://github.com/ansible/community/blob/master/PR-FLOW.md

[ansibot]

cc @haroldwongms @tstringer
click here for bot help

[xkrt]

"Priority integer" issue resolved with #27354

[dagwieers]

There is a light at the end of the tunnel. We made a change to Jinja2 so we don't see all variable types changed into strings. See: pallets/jinja#708