Fix reading resource params with nested spec

[ggverma]

In Policy modules, the resources are nested. Because of this, we read the resource params from the supplied Ansible Playbook and manually validate it with the resource spec. However, we were not reading the resource params correctly if they were nested. This patch fixes that issue. In addition, we convert the new resource params and existing resource params into Ordered Data so that we can compare them and infer if there are any updates with better accuracy

Issue: #417

[vmwclabot]

@ggverma, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 8c66434 must be signed by [email protected]

[salv-orlando]

This might deserve a comment for improving readability.

for instance - assuming that if the first element of the list is a dict, then all the other element will be dicts as well

[ggverma]

Sure, they will be dict though because spec looks like this in such case:

                next_hops=dict(
                    required=True,
                    type='list', <--------- current_spec_type
                    elements='dict', <--- elements can be all str, dict, or list. This defaults to str
                    options=dict(
                        admin_distance=dict(
                            type='int',
                            default=1
                        ),
                        ip_address=dict(
                            type='str'
                        ),
                        scope=dict(
                            type='list',
                            elements='str'
                        )
                    )
                ),

I have updated the condition so that the comment is not needed.

[vmwclabot]

@ggverma, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit abd588d must be signed by [email protected]

[vmwclabot]

@ggverma, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit fe3345e must be signed by [email protected]

[brosenqvist]

this fixes a problem I had with bridge_profiles in segments not being idempotent, but creates issues with tier0, in which is throws KeyError: 'edge_node_info', been trying to resolve, but failing. Any help would be great