refactor(errs): migrate from gperr.Error to standard Go error interface

This is a large-scale refactoring across the codebase that replaces the custom
`gperr.Error` type with Go's standard `error` interface. The changes include:

- Replacing `gperr.Error` return types with `error` in function signatures
- Using `errors.New()` and `fmt.Errorf()` instead of `gperr.New()` and `gperr.Errorf()`
- Using `%w` format verb for error wrapping instead of `.With()` method
- Replacing `gperr.Subject()` calls with `gperr.PrependSubject()`
- Converting error logging from `gperr.Log*()` functions to zerolog's `.Err().Msg()` pattern
- Update NewLogger to handle multiline error message
- Updating `goutils` submodule to latest commit

This refactoring aligns with Go idioms and removes the dependency on
custom error handling abstractions in favor of standard library patterns.

internal/types/routes.go

@@ -8,7 +8,6 @@ import (
 	"github.com/yusing/godoxy/internal/homepage"
 	nettypes "github.com/yusing/godoxy/internal/net/types"
 	provider "github.com/yusing/godoxy/internal/route/provider/types"
-	gperr "github.com/yusing/goutils/errs"
 	"github.com/yusing/goutils/http/reverseproxy"
 	"github.com/yusing/goutils/pool"
 	"github.com/yusing/goutils/task"
@@ -66,8 +65,8 @@ type (
 		Stream() nettypes.Stream
 	}
 	RouteProvider interface {
-		Start(task.Parent) gperr.Error
-		LoadRoutes() gperr.Error
+		Start(parent task.Parent) error
+		LoadRoutes() error
 		GetRoute(alias string) (r Route, ok bool)
 		// should be used like `for _, r := range p.IterRoutes` (no braces), not calling it directly
 		IterRoutes(yield func(alias string, r Route) bool)