libazureinit currently does not bounce DHCP to publish hostname to Azure platform DNS

## Description

Due to starting late (after network-online), azure-init ends up setting the computer name after DHCP. This has the side effect of not registering the correct hostname to DNS (as the image's stale hostname was what got sent in DHCP).

## Impact

Hostname lookup for this VM will fail for other VMs that are in the same VNET or part of VNET peering.

## Additional Information
This won't be an issue if we solve #35. Otherwise we'll have to restart network stack (e.g., NetworkManager)