test: add LoadViewsFrom named-template rendering coverage (framework#989)

[goravel-coder]

Summary

• Render a named template registered via View().LoadViewsFrom() on a new /package-auth route, so package view directories work end-to-end over HTTP.
• Add a dual-driver feature test (TestLoadViewsFrom_NamedTemplate) in HttpTestSuite that asserts the named template renders correctly under both the gin and fiber drivers.
• Pin the gin and fiber drivers to the commits that fix named-template rendering for LoadViewsFrom() (fix: [#989] defer view template compilation to first serve call gin#241, fix: defer default view template compilation to first Run/Listen/Test call fiber#296).

Closes goravel/goravel#989

Why

View().LoadViewsFrom() lets packages register their own view directories, but the gin and fiber drivers were silently dropping named templates ({{ define "auth.tmpl" }}) loaded from those directories. This change pins the fixing driver commits and adds an end-to-end test proving the behavior under both drivers.

// packages/viewtest/service_provider.go — register a package view directory
func (r *ServiceProvider) Boot(app foundation.Application) {
	facades.View().LoadViewsFrom(path.Base("packages", "viewtest", "views"))
}

// routes/web.go — render a named template loaded from that directory
facades.Route().Get("package-auth", func(ctx http.Context) http.Response {
	return ctx.Response().View().Make("auth.tmpl", map[string]any{
		"name": "Goravel",
	})
})

The template auth.tmpl exists only in the LoadViewsFrom-registered directory, so before the driver fixes /package-auth returned nothing; with the pinned fixes it renders under both drivers, and the test locks that behavior in.