Move timing from run scenario

[datejada]

Pull request details

Describe the changes made in this pull request

Reallocate timing out of the scenario function

List of related issues or pull requests

Closes #667

Collaboration confirmation

As a contributor I confirm

• I read and followed the instructions in README.dev.md
• [NA] The documentation is up to date with the changes introduced in this Pull Request (or NA)
• Tests are passing
• Lint is passing

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (5aee7e5) to head (d660af5).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #670   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           16        16           
  Lines          788       789    +1     
=========================================
+ Hits           788       789    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[abelsiqueira]

Nice. I was gonna say that maybe we should try to move to to inside EnergyProblem, but it is used independently in other places as well, so maybe that won't be easy or good.
One thing that I noticed is that we can use the timer from to itself directly, like this:

time_in_seconds = TimerOutputs.time(to["time to create blah"]) / 1e9

So maybe we could use only to and no @elapsed, but keep to as a global variable so that it is used in other places. At this point it doesn't seem really relevant what is the best, so let's keep it like this.