feat: new #[derive(IntoEngineData)] proc macro

[zachschuermann]

What changes are proposed in this pull request?

With the introduction of EvaluationHandler::create_one, we can create EngineData now. This PR adds a handy new procedural macro to implement a new IntoEngineData trait which allows for self.into_engine_data(&dyn Engine) as long as the struct implements ToSchema (usually via #[derive(Schema)]) and all fields implement Into<Scalar>

Few open questions:

1. do we want to consume self and do into_engine_data(self, &engine)? I propose yes, then we can avoid copies in the case the user is actually done with the original struct.
2. should the trait require bounds like T: ToSchema and all fields impl Into<Scalar>? where is the best place to enforce that?

How was this change tested?

new UT

[codecov]

Codecov Report

Attention: Patch coverage is 79.78723% with 19 lines in your changes missing coverage. Please review.

Project coverage is 85.01%. Comparing base (33f36f5) to head (52f3eda).

Files with missing lines	Patch %	Lines
derive-macros/src/lib.rs	72.09%	12 Missing ⚠️
kernel/src/actions/mod.rs	86.95%	6 Missing ⚠️
kernel/src/expressions/scalars.rs	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #830      +/-   ##
==========================================
- Coverage   85.02%   85.01%   -0.01%     
==========================================
  Files          84       84              
  Lines       20637    20731      +94     
  Branches    20637    20731      +94     
==========================================
+ Hits        17546    17625      +79     
- Misses       2226     2241      +15     
  Partials      865      865              

☔ 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.