restrict inclusion of test dependencies to test environment only

We were having some issues in our build pipeline once our Draper-enabled code reached our first production-like environment as the test dependencies weren't available to it.. We have a  number of similar prod-like environments (which use varying Rails.env values), and were wondering what your thoughts are on this change - which worked for us..