fix: max depth issues

[cmilesdev]

Changes

• Adjusted max‑depth behavior to truncate only complex container types at the depth boundary while still printing scalar fields.
• Fixed Stringer/max‑depth interaction so Stringers no longer bypass depth limits, and nil values render consistently.
• Expanded max‑depth test coverage across maps, slices, arrays, pointers, interfaces, and nil containers.

Addresses #45

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[ccoVeille]

Even if quite no one use complex integers in Go it's a thing. So here, I feel like the wording could be different.

But I don't have better wording that "complicated" but it may sound strange too

[ccoVeille]

Any reason to do not do this ?

Suggested change

	for {
	switch v.Kind() {
	case reflect.Interface:
	if v.IsNil() {
	return 0, false
	}
	v = v.Elem()
	case reflect.Ptr:
	if v.IsNil() {
	return 0, false
	}
	v = v.Elem()
	default:
	switch v.Kind() {
	case reflect.Struct, reflect.Map, reflect.Slice, reflect.Array:
	return v.Kind(), true
	default:
	return 0, false
	}
	}
	}
	for {
	switch v.Kind() {
	case reflect.Interface:
	if v.IsNil() {
	return 0, false
	}
	v = v.Elem()
	case reflect.Ptr:
	if v.IsNil() {
	return 0, false
	}
	v = v.Elem()
	case reflect.Struct, reflect.Map, reflect.Slice, reflect.Array:
	return v.Kind(), true
	default:
	return 0, false
	}
	}