Configure Abiquo properties for static IP injection

To configure guest setup to use static IP addresses when DCHP is not available, set the following properties.

For Windows, to use static IP addresses, use a custom specification instead of an unattend file
1. On the Remote Services server and on the API Server
2. Edit the abiquo.properties files and set the property to ignore the unattend file
```
com.abiquo.esxi.experimental.customize.win.unattendfile=false 
```
For Windows, configure the time zone for your custom specification. You can set a timezone for each datacenter, because it is set for the Remote Services. The default value of 110 represents "Western Europe Standard Time"
1. Get the code for your time zone. See https://docs.vmware.com/en/vRealize-Orchestrator/5.5.2/com.vmware.vsphere.vco_use_plugins.doc/GUID-83EBD74D-B5EC-4A0A-B54E-8E45BE2928C2.html
2. On the Remote Services server, edit the abiquo.properties file, and add the following property.
```
com.abiquo.esxi.experimental.customize.win.timezone=110
```
For Windows, to require users to enter the correct VM password when adding a NIC to a deployed VM, set a value for the password wait timeout. If the user enters an incorrect password, the reconfigure will fail and the CMP will roll back the changes to the VM.
1. To require a correct VM password, on the Remote Services server, edit the abiquo.properties file, and add the following property with a value greater than 0.
```
com.abiquo.esxi.experimental.customize.waitpassword.timeoutms=900000
```
  The recommended value is 900000 milliseconds, which is 15 minutes.
  
  By default, the customize.waitpassword.timeoutms property is set to 0 and the CMP will not check the password and it will overwrite the existing administrator password and set the password entered by the user as the new administrator password.
2. You can also change the default time to wait between checks when checking if guest tools has applied the new password
```
com.abiquo.esxi.experimental.customize.waitpassword.periodms=10000
```
For Linux, Abiquo will use the above waitpassword properties to prevent user access to a newly deployed VM until the user can access the VM with the initial password.
For Linux, you can also change the default number of times to validate the template credentials.
```
com.abiquo.esxi.experimental.customize.configure.currentloginretry=5
```

For Windows and Linux, you can also configure these additional properties for your environment to ensure the operating system has time to start up and run guest tools.

# Time in milliseconds to wait for guest tools to be running after power on. The default value is 15 minutes
com.abiquo.esxi.experimental.customize.configure.timeoutms=900000

# Time in milliseconds to wait between checks when checking if guest tools is running after power on
com.abiquo.esxi.experimental.customize.configure.periodms=10000