Add -trimpath flag

[mfridman]

This flag allows the caller to trim the package name which gets displayed in both the package table and tests table.

There's a special case for -trimpath=auto to find the longest common path and use that as the prefix to trim. Almost always this is what a user would want (I think).

Fix #125

Filed a separate issue for the packages that are not being omitted (no tests), #126

Examples:

go test -count=1 ./internal/... -cover -json | tparse

┌──────────────────────────────────────────────────────────────────────────────────────────────┐
│  STATUS │ ELAPSED │                  PACKAGE                  │ COVER  │ PASS │ FAIL │ SKIP  │
│─────────┼─────────┼───────────────────────────────────────────┼────────┼──────┼──────┼───────│
│  PASS   │  0.00s  │ github.com/mfridman/tparse/internal/app   │  0.0%  │  0   │  0   │  0    │
│  PASS   │  0.00s  │ github.com/mfridman/tparse/internal/check │  0.0%  │  0   │  0   │  0    │
│  PASS   │  0.21s  │ github.com/mfridman/tparse/internal/utils │ 100.0% │  11  │  0   │  0    │
└──────────────────────────────────────────────────────────────────────────────────────────────┘

go test -count=1 ./internal/... -cover -json | tparse -trimpath=github.com/mfridman/tparse/

┌───────────────────────────────────────────────────────────────────┐
│  STATUS │ ELAPSED │    PACKAGE     │ COVER  │ PASS │ FAIL │ SKIP  │
│─────────┼─────────┼────────────────┼────────┼──────┼──────┼───────│
│  PASS   │  0.00s  │ internal/app   │  0.0%  │  0   │  0   │  0    │
│  PASS   │  0.00s  │ internal/check │  0.0%  │  0   │  0   │  0    │
│  PASS   │  0.21s  │ internal/utils │ 100.0% │  11  │  0   │  0    │
└───────────────────────────────────────────────────────────────────┘

go test -count=1 ./internal/... -cover -json | tparse -trimpath=github.com/mfridman/tparse/internal

┌────────────────────────────────────────────────────────────┐
│  STATUS │ ELAPSED │ PACKAGE │ COVER  │ PASS │ FAIL │ SKIP  │
│─────────┼─────────┼─────────┼────────┼──────┼──────┼───────│
│  PASS   │  0.00s  │ /app    │  0.0%  │  0   │  0   │  0    │
│  PASS   │  0.00s  │ /check  │  0.0%  │  0   │  0   │  0    │
│  PASS   │  0.21s  │ /utils  │ 100.0% │  11  │  0   │  0    │
└────────────────────────────────────────────────────────────┘

go test -count=1 ./internal/... -cover -json | tparse -trimpath=auto

┌────────────────────────────────────────────────────────────┐
│  STATUS │ ELAPSED │ PACKAGE │ COVER  │ PASS │ FAIL │ SKIP  │
│─────────┼─────────┼─────────┼────────┼──────┼──────┼───────│
│  PASS   │  0.01s  │ app     │  0.0%  │  0   │  0   │  0    │
│  PASS   │  0.01s  │ check   │  0.0%  │  0   │  0   │  0    │
│  PASS   │  0.20s  │ utils   │ 100.0% │  11  │  0   │  0    │
└────────────────────────────────────────────────────────────┘

[mfridman]

There's a few common functions that are fairly important, so I'd like to isolate them into a utils package and add proper tests.

[ccoVeille]

A few minor suggestions

[ccoVeille]

Maybe a comment here, there is one for other variable

[ccoVeille]

I would have used

Suggested change

	elapsed := strconv.FormatFloat(pkg.Summary.Elapsed, 'f', 2, 64) + "s"
	elapsed := pkg.Summary.Elapsed.Truncate(10 * time.Millisecond).String()

[mfridman]

Elapsed is a float64, using strconv.FormatFloat seems most appropriate. If it were time.Time then truncate would probably make more sense.

[ccoVeille]

Oh indeed, I missed that.

[ccoVeille]

What happens if the path is something like

foo/bar/foo

Or something like that, my point is if the first last are equal.

I could happen when the project has a replace in the go.mod file to rewrite long project URLs to something shorter

[mfridman]

It depends on what the other paths are. I added a test case just in case, but this is what I'd expect:

{
	paths: []string{
		"foo/bar/foo",
		"foo/foo/foo",
	},
	want: "foo/",
},