cleaning up azure_rm_deployment samples & return value doc

[zikalino]

SUMMARY

Just some naming conventions, etc.
Added name parameter in every sample
Removed some unnecessary things like subscription_id
Fixed & extended return value documentation

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

azure_rm_deployment

ADDITIONAL INFORMATION

[ansibot]

cc @devigned @haroldwongms @lmazuel @nitzmahone @obsoleted @trstringer @xscript @yuwzho
click here for bot help

[mattclay]

CI failure in integration tests: https://app.shippable.com/github/ansible/ansible/runs/112336/87/tests

[yungezz]

return always? what if my arm template doesn't contain VM?

[zikalino]

well, field is always returned, it may just be empty []

[yungezz]

it's confusing, such as public ip marked as returned always also.

[zikalino]

yes, the lists are always returned, just may be empty,
maybe we could have:
returned: always but list may be empty

or just
returned when applicable

[zikalino]

I actually think "instances" return value should be made obsolete.
it works only with vms.
if somebody uses ARM templates to deploy anything else than VM it's pretty much useless.
we could think of more universal approach.

Usually outputs should be sufficient to use created resources. For instance for Windows VM, outputs look like:

            "outputs": {
                "hostname": {
                    "type": "String",
                    "value": "zimsdplxxxx.eastus2.cloudapp.azure.com"
                }
            }

So it has sufficient information to use the VM.
Outputs are designed by ARM template authors so it's up to them what's important for the user.