Add gas tests for sierra-gas tracked resource

[THenry14]

Related to #2977

This PR stack aims to add support for new resource tracking (sierra-gas) and new gas representation (GasVector triplet instead of single l1 gas value).

-- (#3049) Add sierra gas tracking
-- (#3050) Run already existing tests with CairoSteps set explicitly
-- (#3051) Add support for sierra gas in --detailed-resources
-- (#3052) Add support for sierra gas in --save-trace-data
-- (#3053) Add sierra version assertion
-- (#3054) Introduce new gas representation
--> (This PR) Add gas tests for sierra-gas tracking
-- (#3056) Update docs with sierra-gas related changes

[ddoktorski]

Even with Scarb 2.11.1 some of these tests already fail. Based on our experience so far, such tests seem unmaintainable in the long run. I don't have a specific idea on how to test gas related features, but could we at least assert all values with some acceptable margin? 🙏

cc @cptartur

[THenry14]

Even with Scarb 2.11.1 some of these tests already fail. Based on our experience so far, such tests seem unmaintainable in the long run. I don't have a specific idea on how to test gas related features, but could we at least assert all values with some acceptable margin? 🙏

cc @cptartur

You mean that tests fail when you bump scarb? I guess this is something that can be expected right?

but could we at least assert all values with some acceptable margin?

Seems like a brand new issue tbh, not sure this is something that should be introduced here 🤔 It would probably require us to hold a matrix with prices per version? or even worse, writing some heuristic to "guess" the values? It is probably hard to predict how the cost can change.

As I said, I think this is good idea, just not in scope of this issue.