Fix inadvertent glibc upgrade

Apparently in Ansible, `state=latest` is equivalent to performing an `upgrade` of the packages we are installing with the package manager modules. (I'm new to Ansible, so didn't realize this about `state=latest`.  In Chef, the equivalent would be: `package 'foo'` with `action :upgrade`.  The default action is `:install` which just installs the latest version of the package... but does **not** upgrade it!)

So you might be wondering why this really matters...
The problem with this is that we are specifying to upgrade all the build essential packages which includes glibc, which **many** programs and packages on the system rely on, and are linked against.  So upgrading glibc along with all the build dependencies is a non-trivial operation and in most cases is not what we want to be doing here.  Instead we want to just do what `action :install` would do in Chef, which is `state=present` in Ansible-speak.