Create .deb package for Debian-based Linux distros

[Tyriar]

Related (rpm): #229

[bgse]

Few thoughts on this:

-> 'official' (aka Microsoft-Branded) packaging vs. 'community' (OSS-Build) packaging
(community is more or less effort-free as soon as someone decides a package would be nice, MS-branded is obviously cooler for those who prefer getting it directly from creator and want the neat logo)

-> best executable name?
(I prefer the Fedora COPR over the official releases simply because its executable is named 'vscode' which is cleaner in path than 'code' or 'Code')

[Tyriar]

@bgse I looked a little at what Atom does with regards to this in atom/atom#2956. They distribute a .deb package and have ambitions of eventually having the .deb package register a repository. This is likely the path we will take as well for auto update support.

On executable, the plan is to expose a code wrapper script which calls Code in background and redirects output away from the terminal. You will be able to create an alias or rename the code script to vscode if you want. Not sure we would change the executable name at this point, feel free to open an issue to get a wider perspective though.

[bgse]

@Tyriar Aliasing doesn't really solve the issue properly imo, renaming post-install is a fair point, but then I'd have to ask myself why I'd take the official repo over a community repo that possibly spares me of the hassle. Taking this to #2722 though as to not pollute your issue.