use azure VM resource name as name in boundary

[jwueste]

As mentioned in issue #1821 in boundary project (hashicorp/boundary#1821), dynamic host catalogs are nearly unusable via admin console or desktop app, because discovered hosts don't get a human identifiable name. Only internal id is displayed.
With this PR, the azure resource name is used as hostname in azure.

[hashicorp-cla]

All committers have signed the CLA.

[talanknight]

Thank you so much for your contribution @jwueste ! My understanding is that the last segment of an Azure resource id is not guaranteed to be unique across resource types or resource groups. Is that correct?
If so having the Boundary resource's name be the last part of the azure resource id could cause uniqueness constraint violations in Boundary since Boundary requires all hosts in a specific host catalog to have a unique name. We potentially will want to be able to sync in more resource types beyond just VMs and, as far as I'm aware, Azure does not constrain resource names across resource types.

[stefan-caraiman]

Are there any plans on offering a way to get a human friendly name to show up in the hosts section? If the problem is that Azure does not ensure uniqueness across Resource groups and cross other resources, can't we just add the resource name as a new field which does not have this constraint? 🤔
What do you think @talanknight @jwueste ?

[xingluw]

Hi @stefan-caraiman, we are actively looking at resolving it in the way you described, you can track updates in #1821

[hugoghx]

Hello @jwueste, we have took on this task internally and I just merged changes on this so I'll be closing this for #11. Thanks for doing this!