dpl/dpo: rework metrics

[gudeh]

Summary

This PR includes new metrics for DPL and DPO, including:

• The algorithm used for DPL, being diamond search or negotiation (detailedplace__dpl__legalizer__type).
• Counting of internal DPL moves performed (detailedplace__dpl__total__moves).
  • The diamond search DPL methodology should have the same number of movable instances as the number of internal moves. We only move each cell once. If one move fails, DPL as a whole fails.
  • While the new negotiation approach may have a lot more internal moves, since it allows for overlaps along the algorithm progression.
• Move attempts from DPO (detailedplace__dpo__total__attempts).
• Actually moved instances by DPO (detailedplace__dpo__relocated__cells).
• Displacement data for DPO (max, mean, and total, same as previously available from DPL).

I renamed a few existing metrics, such as from detailedplace__design__instance__displacement__total to detailedplace__dpl__instance__displacement__total

Here is the final result, comparing to master (left):

Type of Change

• Refactoring

Impact

no-op

Verification

• I have verified that the local build succeeds (./etc/Build.sh).
• I have run the relevant tests and they pass.
• My code follows the repository's formatting guidelines.
• I have signed my commits (DCO).

[gemini-code-assist]

Code Review

This pull request enhances placement analysis by introducing move and attempt tracking across legalization and optimization passes. It refactors reporting logic to include detailed displacement statistics and relocated cell counts, while also updating metric names for better consistency. Review feedback focuses on improving code robustness and style by explicitly including the header, using the std::round function, and standardizing DPO metric names to match the updated DPL naming convention.

[github-actions]

clang-tidy made some suggestions

[github-actions]

clang-tidy made some suggestions

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 21 days if no further activity occurs. Remove the Stale label or comment to keep it open.