Fix dynamic MP logic a bit

[84634E1A607A]

Description

(This is added because the complexity of Dyn MP.)
Previously, Dyn MP uses a way similar to bubble sort to check if the action data can be merged together. Which means:

1. Place 1
2. Place 2
3. Remove 2

May be merged into

1. Move 2 -> 1
2. Place 2

This PR aims to make combine operation more optimal by adding a key function GetLeastCostCombineTuple.

Given the data to combine and a list of actions that may be combined to, this function calculates the cost saved by combination for each action and picks the one that saves the most. Then it returns some relevant info.

Related Issues

Extensive testing is needed to prove if this fixes #3558
Workaround #3661

Progress Checklist

Note: before starting this checklist the PR should be marked as non-draft.

• PR author has checked that this PR works as intended and doesn't
  break existing features:
  https://wiki.revolutionarygamesstudio.com/wiki/Testing_Checklist
  (this is important as to not waste the time of Thrive team
  members reviewing this PR)
• Initial code review passed (this and further items should not be checked by the PR author)
• Functionality is confirmed working by another person (see above checklist link)
• Final code review is passed and code conforms to the
  styleguide.

Before merging all CI jobs should finish on this PR without errors, if
there are automatically detected style issues they should be fixed by
the PR author. Merging must follow our
styleguide.

[hhyyrylainen]

I just playtested this and it seems to not at least break anything in a major way so once the code is cleaned up a bit I think this can be merged.