Don't use the cache in admin budget stats

In commit e51e03446, we started using the same code to show stats in the
public area and in the admin area. However, in doing so we introduced a
bug, since stats in the public area are only shown after a certain part
of the process has finished, meaning the stats appearing on the page
never change (in theory), so it's perfectly fine to cache them. However,
in the admin area stats can be accessed while the process is still
ongoing, so caching the stats will lead to the wrong results being
displayed.

We've thought about expiring the cache when new supports or ballot lines
are added; however, that means the methods calculating the stats for the
supporting phase would expire when supports are added/removed but the
methods calculating the stats for the voting phase would expire when
ballot lines are added/removed. It gets even more complex because the
`headings` method calculates stats for both the supporting and the
voting phases.

So, since loading stats in the admin section is fast even without the
cache because they only load very basic statistics, we're taking the
simple approach of disabling the cache in this case, so everything works
the same way it did before commit e51e03446.

Co-authored-by: Javi Martín <javim@elretirao.net>

app/components/admin/stats/budget_balloting_component.rb

@@ -8,7 +8,7 @@ class Admin::Stats::BudgetBallotingComponent < ApplicationComponent
   private
 
     def stats
-      @stats ||= Budget::Stats.new(budget)
+      @stats ||= Budget::Stats.new(budget, cache: false)
     end
 
     def headings_stats

app/components/admin/stats/budget_supporting_component.rb

@@ -8,7 +8,7 @@ class Admin::Stats::BudgetSupportingComponent < ApplicationComponent
   private
 
     def stats
-      @stats ||= Budget::Stats.new(budget)
+      @stats ||= Budget::Stats.new(budget, cache: false)
     end
 
     def headings_stats