Fix Fatal error on Class 'Illuminate\Filesystem' load

Obfuscate to only characters < 128. For protect this method will break UTF-8 string.

Reset indentation and sort words

Fixes laravel#56152 which was caused by the incorrect parameters being used for a more specific type hint docblock merged in laravel#55687. 

This currently causes issues with projects that use static analysis and make use of the $builder->blueprintResolver() method to resolve custom blueprints.

Example below:

 ------ ---------------------------------------------------------------------------------------------------------- 
  Line   Database/DatabaseServiceProvider.php                                                                      
 ------ ---------------------------------------------------------------------------------------------------------- 
  :109   Parameter laravel#1 $connection of class Winter\Storm\Database\Schema\Blueprint constructor expects              
         Illuminate\Database\Connection, string given.                                                             
         🪪  argument.type                                                                                         
  :109   Parameter laravel#2 $table of class Winter\Storm\Database\Schema\Blueprint constructor expects string, Closure   
         given.                                                                                                    
         🪪  argument.type                                                                                         
  :109   Parameter laravel#3 $callback of class Winter\Storm\Database\Schema\Blueprint constructor expects Closure|null,  
         string given.                                                                                             
         🪪  argument.type                                                                                         
 ------ ----------------------------------------------------------------------------------------------------------

* Fix incorrect docblock for custom builder resolvers

Fixes #56152 which was caused by the incorrect parameters being used for a more specific type hint docblock merged in #55687. 

This currently causes issues with projects that use static analysis and make use of the $builder->blueprintResolver() method to resolve custom blueprints.

Example below:

 ------ ---------------------------------------------------------------------------------------------------------- 
  Line   Database/DatabaseServiceProvider.php                                                                      
 ------ ---------------------------------------------------------------------------------------------------------- 
  :109   Parameter #1 $connection of class Winter\Storm\Database\Schema\Blueprint constructor expects              
         Illuminate\Database\Connection, string given.                                                             
         🪪  argument.type                                                                                         
  :109   Parameter #2 $table of class Winter\Storm\Database\Schema\Blueprint constructor expects string, Closure   
         given.                                                                                                    
         🪪  argument.type                                                                                         
  :109   Parameter #3 $callback of class Winter\Storm\Database\Schema\Blueprint constructor expects Closure|null,  
         string given.                                                                                             
         🪪  argument.type                                                                                         
 ------ ----------------------------------------------------------------------------------------------------------

* Update src/Illuminate/Database/Schema/Builder.php

* Apply suggestions from code review

…f type string is deprecated

…f type string is deprecated

…f type string is deprecated

…f type string is deprecated

	- preg_match(): Passing null to parameter laravel#2 ($subject) of type string is deprecated

-  Passing null to parameter laravel#2 ($subject) of type string is deprecated

-  Passing null to parameter laravel#2 ($subject) of type string is deprecated

-  Passing null to parameter laravel#2 ($subject) of type string is deprecated

Pivoted analysis from fixes to new features and API improvements.
Identified 60+ high-value feature opportunities across 6 categories:

KEY FINDINGS:
- 15 API symmetry gaps (missing counterpart methods)
- 10 missing Blade directives for common patterns
- 8 missing validation rules
- 20+ missing testing helpers
- 15 Artisan command enhancements
- 11 convenience methods to reduce verbose patterns

TOP 5 FEATURE OPPORTUNITIES:

laravel#1: Add unless* methods to Stringable (IMPACT: 9/10, MERGE: 10/10)
- Stringable has 15 when* methods but ZERO unless* counterparts
- Collection already has unlessEmpty/unlessNotEmpty
- Perfect API symmetry opportunity

laravel#2: Add @Active Blade directive (IMPACT: 10/10, MERGE: 9/10)
- Used in 95%+ of Laravel apps for navigation
- Reduces verbose ternaries: @Active(condition) vs {{ condition ? 'active' : '' }}
- 30-100 lines saved per navigation component

laravel#3: Add --json to queue:failed command (IMPACT: 9/10, MERGE: 9/10)
- Critical for CI/CD pipelines and monitoring
- Follows recent pattern (schedule:list got --json in Nov 2025)

laravel#4: Add filtering to queue:failed (IMPACT: 9/10, MERGE: 9/10)
- Currently zero options, shows ALL jobs (could be thousands)
- Add --queue, --connection, --after, --class filters
- Follows route:list gold standard pattern

laravel#5: Add phone/positive/negative validation rules (IMPACT: 8/10, MERGE: 9/10)
- 'encoding' rule just added Nov 2025 - same pattern
- Phone is top 5 most common regex validation
- Number sign validation in 50%+ of business apps

RECENT FEATURE ACCEPTANCE PATTERNS:
- API symmetry additions: ~100% merge rate
- Small Blade directives: 90%+ acceptance
- Validation rules: 85%+ acceptance
- Command enhancements: 80%+ acceptance
- Testing helpers: 90%+ acceptance

Document includes:
- Top 15 ranked features with implementation details
- 5-phase implementation roadmap (6 months)
- Ready-to-submit PR template for first feature
- Code examples and file locations for each
- Recent merge patterns analysis
- Success factors and what to avoid

Total estimated: 50+ feature PRs over 6 months

[UPD] Route name alias laravel#2