(RAZOR-362) Remove saucy from build defaults

This commit removes saucy from build_defaults. It went EOL on July 17,
2014
Fix Trusty's preseed file's url to squashfs

The previous squashfs file was pointing to a local file path on the razor
server, rather than a URL to that file.

Fixes https://tickets.puppetlabs.com/browse/RAZOR-365
Remove `all` from `update-node-metadata`

The `all` parameter was previously not functional. It was not mentioned in
the API.md document. It was declared as a valid boolean parameter, but had no
effect on the execution of the command. This removes that superfluous
parameter.

Fixes https://tickets.puppetlabs.com/browse/RAZOR-364
Ubuntu Precise task encounters error

On Ubuntu Precise, the error: "mirror does not support the specified release"
occurs. Turns out this is due to a change to how the preseed file is fetched.
Trusty works fine with the current config, so this will change Lucid and
Precise back to the last working version.

This commit follows the decision that the base task should be kept most
up-to-date, meaning that `ubuntu.task` should currently mimic Trusty.

Fixes https://tickets.puppetlabs.com/browse/RAZOR-366
Update README.md

fixing semver link
Properly handle DOS line endings for WIndows files (no functional change)

Tell git that *.ps1 files are Windows files and should be treated as such.
build-winpe: allow passing in where image and scratch files should be put
build-winpe: adapt to ADK 8.1

Based on https://github.com/nanliu/razor-server/tree/win2012
build-winpe: pass the Razor server URL in at build time

Since there is no way to set the URL of hte Razor server at boot time, we
pass it in at build time as a command line argument to the
build-razor-winpe script
Installer for Windows 2012 R2

Fixes https://tickets.puppetlabs.com/browse/RAZOR-353
* build-winpe/razor-client.ps1: retry the initial contact to the Razor server

Sometimes, at least on my network, the first few attempts at accessing
/svc/nodeid fail, presumably because the network isn't fully up yet. To
mitigate that, try to contact the Razor server up to 10 times, with 3s
pause in between.