Use Active Storage to handle cached attachments

This fixes a few issues we've had for years.

First, when attaching an image and then sending a form with validation
errors, the image preview would not be rendered when the form was
displayed once again. Now it's rendered as expected.

Second, when attaching an image, removing it, and attaching a new
one, browsers were displaying the image preview of the first one. That's
because Paperclip generated the same URL from both files (as they both
had the same hash data and prefix). Browsers usually cache images and
render the cached image when getting the same URL.

Since now we're storing each image in a different Blob, the images have
different URLs and so the preview of the second one is correctly
displayed.

Finally, when users downloaded a document, they were getting files with
a very long hexadecimal hash as filename. Now they get the original
filename.

spec/models/direct_upload_spec.rb

@@ -34,13 +34,14 @@ describe DirectUpload do
   end
 
   context "save_attachment" do
-    it "saves uploaded file" do
-      proposal_document_direct_upload = build(:direct_upload, :proposal, :documents)
+    it "saves uploaded file without creating an attachment record" do
+      direct_upload = build(:direct_upload, :proposal, :documents)
 
-      proposal_document_direct_upload.save_attachment
+      direct_upload.save_attachment
 
-      expect(File.exist?(proposal_document_direct_upload.relation.attachment.path)).to eq(true)
-      expect(proposal_document_direct_upload.relation.attachment.path).to include("cached_attachments")
+      expect(File.exist?(direct_upload.relation.file_path)).to be true
+      expect(direct_upload.relation.storage_attachment.blob).to be_persisted
+      expect(direct_upload.relation.storage_attachment.attachment).not_to be_persisted
     end
   end
 end