Dont use ssl cookies on tests or dev

[related #680] - It doesnt fix the issue in production, as it is a
clearance issue, but it resolves it in development and test.

development/test has no ssl certificate so setting cookies in that scope is pointless and confusing as the cookies will not be persisted.
This change is necessary for rails 4+ , as the capybara tests were failing because the server in there is not https, and it was losing the session, as no cookie set. Not sure why it works under 3.2, it might be some rails bug where they mix secure and unsecure cookies(which was fixed on 4+). Regardless, the right thing to do is not use ssl cookies locally. (see https://github.com/rubygems/rubygems.org/issues/680#issuecomment-64927047)

cc @derekprior @knappe
r. @dwradcliffe