Fix dependency bounds for dune-action-trace

[shonfeder]

Necessary for #13674 (as per #13674 (comment))

Followup to #13267

[Alizter]

This library is intended to be public. I'm not following your explanation of with-test however. If you look in otherlibs/dune-action-trace you will see there are tests which ideally should be run wtih with-test. Could you elaborate on what you were observing?

[Alizter]

Specifically the -p dune-action-trace arg to dune will actually remove all the stanzas unrealted to the package from being considered, so only the tests related to dune-action-trace should be run. Even more since the package stanza has a dir field which tells dune only this directory should be considered when filtering for that package.

[shonfeder]

This library is intended to be public. I'm not following your explanation of with-test however. If you look in otherlibs/dune-action-trace you will see there are tests which ideally should be run with with-test.

I'm following the pattern of #12954 -- if the tests are meant to be run during opam installation --with-test, then please fix the tests so that they pull in the required dependencies and/or don't run unrelated code.

Could you elaborate on what you were observing?

https://opam.ci.ocaml.org/github/ocaml/opam-repository/commit/118a690db616b1df5c53d5fa00eb70791a80ae2c/variant/compilers,4.12,dune-action-trace.3.22.0~alpha0,tests

[shonfeder]

I've removed the part of this addressing the test dependencies, and instead filed an issue for that #13732

This way we can get the simplest part here merged, and those with context on the dune-action-trace package can decide how that should be fixed.

[rgrinberg]

You can disable the tests if they're getting in the way of the release. We can always fix them for the next release.