Add Laravel storage disk name intelligence

[shuvroroy]

Summary

Laravel storage disk names now behave like navigable config symbols in every direct storage context:

• Storage::disk()
• Storage::fake() and Storage::persistentFake()
• Scalar and array arguments to Storage::forgetDisk()
• Laravel's #[Storage] contextual attribute, including named arguments

Completion reads filesystems.disks.*; hover and Ctrl+Click resolve the matching config entry; find-references connects storage calls, generic config access, and the config declaration.

Runtime semantics

The diagnostic behavior follows Laravel rather than treating every occurrence as a required config read:

• disk() diagnoses an unknown configured disk.
• fake() and persistentFake() may create ad-hoc test disks, so they remain valid without a declaration.
• forgetDisk() accepts a scalar or array and tolerates names that are not currently configured.

Array keys, nested values, dynamic expressions, unrelated Storage classes, and incorrect named parameters are deliberately excluded.

Why this is separate

This is the focused storage-disk layer split from #368 after review feedback. It contains only the Laravel storage task and its tests, docs, and demo changes.

Depends on:

• Fix filesystem aliases in vendor and Blade discovery #369

The dependency is the independent filesystem-alias fix discovered while testing this work. Once #369 lands, this branch can be rebased and the PR will show only the storage feature.

Verification

• 13,667 tests passed; 2 intentionally skipped
• 734/734 changed executable Rust lines covered (100.00%)
• cargo clippy --all-targets -- -D warnings
• cargo fmt --check
• PHP playground syntax checks and runtime assertions
• Laravel demo syntax check
• Laravel analyzer reports exactly the three intentional demo errors

Checklist

• I have updated CHANGELOG.md
• I have updated the documentation (README.md, docs/, examples/)
• I have updated the config schema (config-schema.json)
• I have added/updated tests to cover my changes
• I fully understand the code that I am submitting (what it does,
  how it works, how it's organized), including any code drafted by an LLM.
• For any prose generated by an LLM, I have proof-read and copy-edited with
  an eye towards deleting anything that is irrelevant, clarifying anything
  that is confusing, and adding details that are relevant. This includes,
  for example, commit descriptions, PR descriptions, and code comments.

🤖 Generated with Codex

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 98.95178% with 10 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/completion/laravel_string_keys.rs	99.12%	4 Missing ⚠️
src/indexing/init.rs	55.55%	4 Missing ⚠️
src/symbol_map/extraction/laravel.rs	99.53%	1 Missing ⚠️
src/virtual_members/laravel/config_keys.rs	98.64%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[shuvroroy]

@AJenbo I already resolved the conflicts for you so it's ready for review again

[AJenbo]

Thanks. I handled some regressions, please make sure it still works as expected