Feature/settlement rewrite

[vstam1]

What?

This Pr removes the old settlement code and replaces it with new functions. This Pr makes the following big changes to the code:
Settlement:

• All previous settlement functions are deleted and replaces with 6 new settlement functions, 3 for successful projects and 3 for failed projects, to settle an evaluation, bid or contribution.
• For each successful project, for each eval, bid, cont -> CT tokens are minted + we calculate the correct Migration data and store this in a new storage item UserMigrations
• All evals, bids and contributions are removed from storage once the settlement is successful.

Migrations:

• Migrations are done per User (1 user can have a total of 48 migrations (16 Evals, 16 Bids, 16 Contributions).
• The functions do_migrate_one_participant takes all the users Migrations and sends them over to the destination chain. The QueryId associated with the Xcm is stored in the ActiveMigrationQueue that stored QueryId -> (project_id, participant) and is used to get the correct information associated with the Query id from the UserMigrations storage.
• UserMigrations stores for each (project, user) pair a tuple of (MigrationStatus, BoundedVec)
• Based on the return status of the QueryId we either set the MigrationStatus to Failed or Confirmed.
• If the migration Failed, a user can restart the Migration again.

Rest:

• Updated the Average Price calculation logic. We do the following things:
  • Split the bids into accepted, rejected.
  • Remove Rejected bids after they have been refunded.
  • After price calculations adjust bids for either:
    • PartiallyAccepted
    • Bids with current price > weighted price
• Remove the "in between" settlement variables from BidInfo and ContributionInfo:
  • For bids and Contributions:
    • funds_released
    • ct_minted
    • ct_migration_status
  • For evaluations:
    • rewarded_or_slashed
    • ct_migration_status
• Removed all "Cleaner" functionalities.

Why?

To improve code maintainability and quality

How?

Testing?

• Most tests in mod funding_end are updated
• All the tests in CT_migrations integration test are updated

Screenshots (optional)

Anything Else?

[lrazovic]

From a preliminary review the code looks good! It is difficult to tell if the logic is 100% correct simply from the code, so I await the e2e test to do a more thorough review.

Besides tests and benchmarks, what features are missing compared to main?

[JuaniRios]

General direction seems very good.
A lot of changes were done, so I focused more on the structure than the internal logic.
A last review should be done after the PR is marked as ready.

When it's marked as ready I would like to see an in-detail description about the most important changes so we are all on the same page. Specially about the migrations. What was happening before, and how it's happening now.

[JuaniRios]

Really really good changes Just, well done!
It feels like we are finally transitioning from a spaghetti to a production-ready codebase.

My main request is to fix the benchmarks cause they aren't working. Try the command just dry-run-benchmarks to see what I mean.

The rest you'll see on the specific comments :)

[JuaniRios]

Missing fixes and tests that will be addressed in future PRs, but lets merge