feat: session.eval_with_hooks

[hugocaillard]

wip - exploring an other interface for session hooks

With this approach:

• the Session is more aware of it's hooks
  • instead of passing eval_hooks to every functions (eval, deploy_contract , call_contract), the caller only enable an hook once
  • in the future we could have session.enable_debug_print_hook, session.enable_tracer_hook, etc
• I added .eval_with_hooks that keeps the same behaviour and is backward compatible with exisintg implementation. It allows to evaluated snippets with arbitrary hooks
  • Should we choose to use the implemation, I should add some documentation in the comments for the eval_with_hooks method

Concerns:

• is the Session supposed to be that aware of the hooks, or is it better to keep them as parameters, so that the Sessionis mor versatile

[hugocaillard]

As a side effect, this is the wanted behaviour for code coverage.
Because session.deploy_contract uses the session coverage hook.
This is therefore the initial analysis of the contracts.
If we wanted to pass the eval_hooks to update_session_with_deployment_plan (here) instead, this would make pass eval_hooks args in a whole lot more of functions (and it comes with some difficulties down the line)

[hugocaillard]

So this a wanted behavior for better coverage handling; It doesn't really impact code coverage % though

[codecov]

Codecov Report

Attention: Patch coverage is 93.04348% with 8 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
components/clarity-repl/src/repl/session.rs	94.93%	4 Missing ⚠️
components/clarinet-deployments/src/onchain/mod.rs	0.00%	2 Missing ⚠️
components/clarinet-cli/src/frontend/dap.rs	0.00%	1 Missing ⚠️
components/clarity-events/src/bin.rs	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!