feat: Move context types to new ctx module (#450)

[jawoznia]

No description provided.

[codecov]

Codecov Report

Attention: Patch coverage is 38.09524% with 13 lines in your changes missing coverage. Please review.

Project coverage is 72.19%. Comparing base (0df5cf9) to head (403bf47).
Report is 3 commits behind head on feat/replies.

Files with missing lines	Patch %	Lines
sylvia/src/ctx.rs	35.29%	11 Missing ⚠️
sylvia-derive/src/entry_points.rs	0.00%	1 Missing ⚠️
sylvia/tests/messages_generation.rs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           feat/replies     #451      +/-   ##
================================================
- Coverage         72.49%   72.19%   -0.30%     
================================================
  Files                62       63       +1     
  Lines              3795     3812      +17     
================================================
+ Hits               2751     2752       +1     
- Misses             1044     1060      +16     

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

[hashedone]

Mostly ok, but I'd like to quickly talk about deprecation order (it's prob right, but I want to double check)

[hashedone]

👍

[hashedone]

Only thing I am wondering right now - do we want to deprecate this struct or do we want to throw a deprecation warning using #[sv::msg(reply)] without #[sv::features(replies)]? I'm not debating on if this is ok to deprecate this, but which one gives back a better warning message (or even error using the wrong context - however I think that the old context could be in fact used with new messages if the proper From is implemented? Or not? Or maybe both could be? Let's chat about it).

[jawoznia]

It might be used if we initialize the context with empty vectors and set the gas to 0. I'm not sure if the detection which ReplyCtx is used would be possible though.

I went with different approach and moved all the context types to new ctx module.

[kulikthebird]

The only comment from me is the one we discussed before - there should be exactly one ReplyCtx that is not deprecated

[kulikthebird]

LGTM!