Proposal to ilmerge cake.exe dependencies

[wwwlicious]

Raising an issue on advice from @gep13 in gitter to promote some discussion

Most CI servers have the concept of uploading tooling/binaries which can be distributed to agents and used during builds.

In order to aid the simplest possible integration with various CI platforms,, it would be easier if cake.exe were available as a single binary executable with any dependencies ilmerged into a standalone binary, available via a nuget package as it currently is, but also via the nuget model (or the one which you currently use in the bootstrapper's to get nuget.exe and packages.config)

If CI plugins are not self-contained, they tend to be fragile in corporate networks that block external access to download additional dependencies. So the goal should be to make them as self-contained as possible.

[Some context]
For my specific purposes, I am looking to create a Cake build plugin for Bamboo which itself has little or no support for nuget, but supports the concept of 'capabilities'. These capabilities can be versioned (like TC supports multiple nuget versions via tooling admin), shared on remote agents and detected/accessed from a Cake Build task but have to be explicitly setup on each agent. I'm trying to figure out the best way to accomplish this without requiring that the plugin downloads anything but instead allows admins to upload or configure versioned tooling capabilities (binaries) on build agents.