Add core_test_utils crate and move core tests there

[GraDKh]

Move test utilities from compute to core

TL;DR

Created a new binius_core_test_utils crate and moved test utilities related to core functionality from binius_compute_test_utils.

What changed?

• Created a new crates/core/test_utils directory with its own Cargo.toml
• Moved the following modules from compute/test_utils to core/test_utils:
  • bivariate_sumcheck
  • piop
  • ring_switch
• Updated imports in affected test files to use the new crate
• Added binius_core_test_utils as a dev-dependency in crates/core/Cargo.toml

How to test?

Run the tests in the core crate to ensure they still pass with the new test utilities:

cargo test -p binius_core

Why make this change?

This change improves the organization of test utilities by placing them closer to the code they're testing. Test utilities specific to core functionality now live in the core crate, making the codebase more modular and easier to maintain.

[GraDKh]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Extract macro to instantiate ring switch tests #785
• Add a macro to instantiate bivariate_sumcheck tests #783
• Introduce macros to instantiate compute layer test #782
• Add core_test_utils crate and move core tests there #781 👈 (View in Graphite)
• Move compute test utils to a different folder #780
• main

---

How to use the Graphite Merge Queue

Add the label merge-ready to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.