Windows updates: seconds attempt

@tmeasday @seanmwalker @sdarnell I think that it's time to create a new pull request so that we can see all changes in one place. I've disabled meteor pinning for Windows and added some line endings heuristics which tries to preserve type of EOLs in `smart.lock`, `smart.json` and `.gitignore` (`os.EOL` is used by default). `meteorite create-project` creates stub project with system-specific EOLs.

No spaces folder:
1. All tests are passed on Linux (126)
2. All tests are passed on Windows (123, yellow warning is displayed before tests)

Folder with spaces (it implies that `HOME` directory have spaces during testing too):
1. Three meteor-pinning tests are failing on Linux because of old Meteor testing versions (these versions themselves are not able to correctly run from folder with spaces).
2. Lots of tests are failing on Windows because of featurist/spawn-cmd#3 (spaces issue). However, creating and working with projects which have spaces in path is OK and works fine, because we run `git` by its name during regular work, not by its absolute path and therefore this path is not getting quoted.

Things left to do:

[ ] - update readme with new information about Meteorite on Windows (don't forget to mention that we use directory junctions and some ancient software may handle it strange)
[ ] - decide what to do with featurist/spawn-cmd#3 It's actually affects testing on Windows only and has nothing to do with regular usage.

Waiting for your comments, code review and thoughts on the second TODO thing.