Remove gems for managing FTP

If all previous commits have deployed, we should now be able to remove the gem that managed our connection to the SFTP server

Author: jonodrew

Gemfile

@@ -9,7 +9,6 @@ gem 'bootsnap', require: false
 
 gem 'acts-as-taggable-on'
 gem 'carrierwave'
-gem 'carrierwave-ftp', github: 'luan/carrierwave-ftp', ref: '5481c13', require: 'carrierwave/storage/sftp'
 gem 'cocoon'
 gem 'delayed_job'
 gem 'delayed_job_active_record'

Gemfile.lock

@@ -1,13 +1,3 @@
-GIT
-  remote: https://github.com/luan/carrierwave-ftp.git
-  revision: 5481c1335fd3285d2057c7056e8a4662daa68dd4
-  ref: 5481c13
-  specs:
-    carrierwave-ftp (0.4.1)
-      carrierwave (>= 0.6.2)
-      double-bag-ftps (~> 0.1.4)
-      net-sftp (~> 4.0.0)
-
 GEM
   remote: https://rubygems.org/
   specs:
@@ -177,7 +167,6 @@ GEM
     dotenv-rails (3.1.0)
       dotenv (= 3.1.0)
       railties (>= 6.1)
-    double-bag-ftps (0.1.4)
     erubi (1.13.1)
     execjs (2.10.0)
     fabrication (2.31.0)
@@ -266,11 +255,8 @@ GEM
       net-protocol
     net-protocol (0.2.2)
       timeout
-    net-sftp (4.0.0)
-      net-ssh (>= 5.0.0, < 8.0.0)
     net-smtp (0.4.0.1)
       net-protocol
-    net-ssh (7.3.0)
     nio4r (2.7.3)
     nokogiri (1.18.9)
       mini_portile2 (~> 2.8.2)
@@ -526,7 +512,6 @@ DEPENDENCIES
   capybara
   carrierwave
   carrierwave-aws (~> 1.6)
-  carrierwave-ftp!
   chosen-rails
   cocoon
   commonmarker