NetCreateProvisioningPackage vs NetProvisionComputerAccount

Hello,

Is there a benefit to migrating from `NetProvisionComputerAccount` to `NetCreateProvisioningPackage` ?

We used `splice` internally as a way to domain join after imaging with Glazier, but we needed the join to set up enough PKI & GPO related stuff that the machines could drop onto an AlwaysOn VPN Device Tunnel once they reboot.

`NetCreateProvisioningPackage` allows you to bundle PKI (including a machine certificate generated & signed as the package is created) and Group Policy, but is also backwards compatible with `NetRequestOfflineDomainJoin` according to the Microsoft docs.

Both `NetCreateProvisioningPackage` and `NetRequestProvisioningPackageInstall` implemented here if it helps:

https://github.com/iamacarpet/go-win64api/blob/master/provisioning.go

Thanks so much for your great project, we'd have never even known this was possible without it :).

Regards,
iamacarpet