[2.x] Move internal Vite hot file to runtime directory for better semantics

[emmadesilva]

Summary

Moves the Vite hot file from the cache directory to a new runtime directory under storage/framework. This aligns better with its actual purpose, as the file is used for runtime signaling, not caching.

Details

• The hot file is now located at storage/framework/runtime/vite.hot.
• The Vite::running() method has been updated to reflect the new path.
• No external user-facing behavior is changed. Framework storage is internal.
• This change prepares the system for potential future runtime or IPC features.

Reasoning

The cache directory is intended for optimizing repeated computations, not for interprocess signaling or ephemeral runtime flags. Using a dedicated runtime directory makes internal filesystem structure clearer and more maintainable over time.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (3b90e57) to head (db037f4).
Report is 11 commits behind head on 2.x-dev.

Additional details and impacted files

@@             Coverage Diff             @@
##             2.x-dev     #2154   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity      1976      1976           
===========================================
  Files            199       199           
  Lines           5282      5282           
===========================================
  Hits            5282      5282           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.