(slow) operations tracker

[joaquimg]

This adds the optional ability to mark all places where slow operations that allocate expression occur. Keeping the stack might be a lot of data, but it is a way to properly identify the issues instead of erroring one by one.

Possible additional functionality:
1 - also mark the operation type. A bit redundant with the stack, but might lead to summary reports.
2 - create a user friendly summary

TODO

• add tests
• add docs session, to be referenced in the performance issues.

[codecov]

Codecov Report

Attention: Patch coverage is 65.41353% with 46 lines in your changes missing coverage. Please review.

Project coverage is 99.25%. Comparing base (57132d8) to head (bd416ee).

Files with missing lines	Patch %	Lines
src/operators.jl	65.41%	46 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##            master    #3970      +/-   ##
===========================================
- Coverage   100.00%   99.25%   -0.75%     
===========================================
  Files           43       43              
  Lines         6076     6207     +131     
===========================================
+ Hits          6076     6161      +85     
- Misses           0       46      +46     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.