Replace ENV.clone mock with empty hash

ENV.clone only performs a shallow-copy of the ENV object. Which means that
`mock_env.clear` wipes the real ENV object and affects other tests that run
after this.

We didn't notice it because this is currently the last test picked up by
`rake integration`, but when we attempted to move it in #108 it made all of
the other tests fail. This can also be tested by placing the following at
the end of this spec file:

    describe 'after' do
      it { expect(ENV.to_hash).to_not eq({}) }
    end

Replace it with an empty hash. While this isn't truly the same as the ENV
object because it doesn't implement all of the same methods it should
suffice for the things that Fog needs.

I don't think the `login_manual.rb` test is affected because it uses
`ENV.to_hash` instead. However, since this test it only run manually, I
don't think it matters that much right now.
Restore Fog.credentials[_path] after test

Store the original values of Fog.credentials and Fog.credentials_path and
restore them after the test. This will prevent this test from rendering Fog
unusable for any tests that follow it.

It can be verified by placing the following at the end of the spec file:

    describe 'after' do
      it { expect(Fog.credentials).to_not eq({}) }
    end
Don't use @real_password in login_spec.rb

This instance variable went with login_manual.rb in ad15254. We don't
actually need the real password to test this effect, so use a plain string.
Merge pull request #110 from gds-operations/76118720-fix_leaky_env_mock

[#76118720] Replace ENV.clone mock with empty hash