feat: [#702] apply fieldalignment & modernize fixes

[almas-x]

📑 Description

Closes goravel/goravel#702

This PR includes automated refactors applied via fieldalignment and modernize to improve code quality and consistency:

• fieldalignment: optimized struct field order for better memory layout
• modernize:
  • efaceany: replaced interface{} with Go 1.18+ any
  • minmax: simplified if-else assignments to built-in min/max
  • rangeint: converted classic for i := 0; i < n; i++ loops to for i := range n
  • fmtappendf, mapsloop, slicescontains: applied equivalent modernizations

✅ Checks

• Added test cases for my code

[Copilot]

Pull Request Overview

This PR applies automated refactors using fieldalignment and modernize to improve code consistency and leverage newer Go features.

• Optimized struct field ordering for better memory layout.
• Replaced interface{} with any and manual loops with slices.Contains, maps.Copy, and fmt.Appendf.
• Simplified min/max logic and classic for i := 0; i < n; i++ loops using modern patterns.

Reviewed Changes

Copilot reviewed 86 out of 86 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
support/process/utils.go	Replaced classic loop with for range 60.
foundation/application.go	Replaced classic loop with for range 50.
database/db/utils.go	Replaced for i := 0; i < length; i++ with for i := range length.
cache/memory_test.go	Updated two for i := 0; i < 1000; i++ loops to for range 1000.
console/cli_helper.go	Replaced manual loop bounds with for index := range lenShared.

Comments suppressed due to low confidence (6)

support/process/utils.go:26

• In Go, you cannot for range over an integer literal. You should restore an index-based loop, e.g., for i := 0; i < 60; i++ {.

	for range 60 {

foundation/application.go:312

• Ranging over an integer is invalid. Change back to a traditional loop or iterate over a slice: for i := 0; i < 50; i++ {.

		for range 50 {

database/db/utils.go:50

• You cannot use range on an integer. Keep for i := 0; i < length; i++ { or range over a slice of that length.

		for i := range length {

cache/memory_test.go:75

• for range cannot iterate an integer. Revert to for i := 0; i < 1000; i++ { for correct iteration.

	for range 1000 {

cache/memory_test.go:183

• Invalid for range over an int. Use a conventional loop: for i := 0; i < 1000; i++ {.

	for range 1000 {

console/cli_helper.go:237

• Cannot range over an int value. Either keep the original index loop or range over a slice/string: for index := 0; index < lenShared; index++ {.

	for index := range lenShared {

[codecov]

Codecov Report

Attention: Patch coverage is 61.11111% with 14 lines in your changes missing coverage. Please review.

Project coverage is 71.16%. Comparing base (9719535) to head (93a8755).
Report is 3 commits behind head on master.

Files with missing lines	Patch %	Lines
foundation/application.go	25.00%	6 Missing and 3 partials ⚠️
support/env/env.go	0.00%	2 Missing ⚠️
validation/validation.go	50.00%	1 Missing and 1 partial ⚠️
testing/http/test_request.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1096      +/-   ##
==========================================
+ Coverage   71.09%   71.16%   +0.06%     
==========================================
  Files         183      183              
  Lines       12854    12826      -28     
==========================================
- Hits         9138     9127      -11     
+ Misses       3345     3330      -15     
+ Partials      371      369       -2     

☔ View full report in Codecov by Sentry.
📢 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.

[hwbrzzl]

Great PR 👍 Is there a script or github action to format files automatically?

[almas-x]

Great PR 👍 Is there a script or github action to format files automatically?

It’s not easy to create a fully automated script for this, unfortunately.

The fieldalignment tool doesn’t exclude _test.go files by default, so some manual cleanup is required. And for modernize, the issues it detects and fixes can vary depending on the Go version, which means we also need to review and filter changes manually.

Because of that, it’s more practical to run these optimizations periodically—such as before major releases—rather than on every commit.

[hwbrzzl]

Great 👍

[hwbrzzl]

Could you add the sort rule to the PR description?