build: Run scala tests against release build of native code

[andygrove]

Which issue does this PR close?

Closes #2540

Rationale for this change

See #2540

What changes are included in this PR?

How are these changes tested?

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.92%. Comparing base (f09f8af) to head (628d16f).
⚠️ Report is 581 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #2541      +/-   ##
============================================
+ Coverage     56.12%   58.92%   +2.79%     
- Complexity      976     1457     +481     
============================================
  Files           119      147      +28     
  Lines         11743    13642    +1899     
  Branches       2251     2369     +118     
============================================
+ Hits           6591     8038    +1447     
- Misses         4012     4381     +369     
- Partials       1140     1223      +83     

☔ 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.

[mbutrovich]

Does this replace an existing CI check? I think we'd want to run in both debug and release (in case we start making more use of things like debug_assert).

[parthchandra]

lgtm

[parthchandra]

Does this replace an existing CI check? I think we'd want to run in both debug and release (in case we start making more use of things like debug_assert).

One option is to parametrize this pipeline and run with the release build only before a release. That increases the burden on the release manager though.

[andygrove]

Does this replace an existing CI check? I think we'd want to run in both debug and release (in case we start making more use of things like debug_assert).

I'd like to go ahead and merge this to unblock some things. I filed a follow-on issue #2544 to discuss this