Remove redundant database checks in system tests

These tests check what happens from the user's point of view. For
instance, we check that after disabling recommendations, they are not
shown. What happens in the database is not related to the user
experience.

Furthermore, checking the database after the browser has started is
proving to be a major source for inconsistent data in specs.

spec/system/proposals_spec.rb

@@ -929,12 +929,9 @@ describe "Proposals" do
         expect(page).not_to have_css(".recommendation", count: 3)
         expect(page).to have_content("Recommendations for proposals are now disabled for this account")
 
-        user.reload
-
         visit account_path
 
         expect(find("#account_recommended_proposals")).not_to be_checked
-        expect(user.recommended_proposals).to be(false)
       end
     end
   end