fix: reorder configureMiddleware before Boot so provider routes survive engine rebuild (#975)

[goravel-coder]

Summary

Fixes goravel/goravel#975

Routes registered inside a ServiceProvider.Boot() (e.g. app.MakeRoute().Get(...)) were silently discarded when the application registered any global middleware via WithMiddleware() in bootstrap/app.go. The routes returned 404 at runtime with no error.

Root Cause

In Build(), configureMiddleware() was called after Boot(). When WithMiddleware is used, SetGlobalMiddleware rebuilds the route engine (gin.New() / equivalent). Routes registered by providers during Boot() were on the old engine and lost.

Fix

Reorder configureMiddleware() to run between Register() and Boot() instead of after Boot():

• Providers register their IoC bindings (including Route facade) → Register()
• Middleware configured, engine initialized with global middleware → configureMiddleware() (moved here)
• Providers register routes on the already-configured engine → Boot()
• App routes via WithRouting also register on the same engine → configureRoutes()

This is a one-line move in foundation/application.go.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 69.63%. Comparing base (d174ca3) to head (8c6802e).

Files with missing lines	Patch %	Lines
foundation/application.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1508   +/-   ##
=======================================
  Coverage   69.63%   69.63%           
=======================================
  Files         384      384           
  Lines       30183    30183           
=======================================
  Hits        21017    21017           
  Misses       8174     8174           
  Partials      992      992           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.