Use Pydantic to manage parameter metadata and validation

[FlxPo]

Pydantic models seem to be a good fit for our needs :

• Works just like the previous dataclasses for the users (ie PopulationTripsParameters(seed=0).
• Handles default values and let us track what the user changed or leaved as default.
• A lot of available metadata fields to document parameters.
• Automatic validation for different situations (float in an one sided / two sided interval, set of str values...).
• Easy export to a serializable dict so can be hashed by the Asset class.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.42%. Comparing base (c8c3ac3) to head (1278b7f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #258   +/-   ##
=======================================
  Coverage   70.42%   70.42%           
=======================================
  Files          56       56           
  Lines        2424     2424           
=======================================
  Hits         1707     1707           
  Misses        717      717           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Mind-the-Cap]

Agreed with Pydantic use!