feat(cli/tools): add a subcommand --hide-stacktraces for test

[Hajime-san]

resolves #24002

I implemented this suggestion that I think it sounds reasonable for reducing noise.
Also, this feature could hide stack trace when running test from editor with LSP command by internal code updated, however I don't touch it currently.

example

• test.ts

import { assert } from "@std/assert/assert";

Deno.test("assert a b", () => {
  assertEquals("foo", "bar");
});

before

% deno test test.ts              
running 1 test from ./test.ts
assert a b ... FAILED (6ms)

 ERRORS 

assert a b => ./test.ts:3:6
error: AssertionError: Values are not equal.


    [Diff] Actual / Expected


-   foo
+   bar


  throw new AssertionError(message);
        ^
    at Module.assertEquals (https://deno.land/[email protected]/assert/assert_equals.ts:52:9)
    at assertEquals (https://deno.land/[email protected]/testing/asserts.ts:101:11)
    at file:///path/to/test.ts:4:3

 FAILURES 

assert a b => ./test.ts:3:6

FAILED | 0 passed | 1 failed (7ms)

error: Test failed

after

% target/debug/deno test --hide-stacktraces test.ts               
Check file:///path/to/test.ts
running 1 test from ./test.ts
assert a b ... FAILED (10ms)

 ERRORS 

assert a b => ./test.ts:3:6
error: AssertionError: Values are not equal.


    [Diff] Actual / Expected


-   foo
+   bar



 FAILURES 

assert a b => ./test.ts:3:6

FAILED | 0 passed | 1 failed (15ms)

error: Test failed

[lucacasonato]

Thanks, just a couple comments. Sorry for the slow review.

[lucacasonato]

Can you rename this option to --hide-stacktraces?

[dsherret]

LGTM. Thanks!

[Hajime-san]

@dsherret
Thank you for updating!