Don't include build-essential just to be sure apt is up to date

[martinb3]

First, build-essential is a big dependency just to avoid ensuring apt and yum are up to date. The apt and yum cookbooks have ways to do that which don't also involve installing autoconf and GCC. I'd argue this is the wrong dependency to include if the goal is to ensure package metadata is up to date. See #88 for how this came to be.

Secondly, build-essential and forcing it run at compile time takes control away from the developer/user; most folks are already following the pattern of ensuring apt or yum is up to date before calling dependent cookbooks, and if we move build-essential to compile time, it actually can create a race condition between what people's wrappers are doing and the elasticsearch cookbook is doing -- we could be moving build-essential in front of gathering apt/yum metadata. That's what happened to me in this report, so now I have autoconf failing to install because build-essential was moved before it due the change above.