Preload redirected routes

Describe the problem

Currently when a link preloads a route that initiates a redirect through one of its server load functions, the subsequent route's code and data are not preloaded. This behavior leads to increased load times for users, as the code and data of links with redirects have not been loaded in the background when a navigation is triggered.

Describe the proposed solution

Preloading a route that issues a redirect should also trigger a preload of its subsequent route. This could be implemented either dynamically on the client side, by triggering another preload request whenever a redirect is encountered, or on the server side, by automatically executing load functions and including the data and code of the final destination in the redirect response.

Alternatives considered

No response

Importance

nice to have

Additional Information

No response

Start by tracing how route preloading handles server load redirects on the client and server. The change is complete when preloading a redirecting route also preloads the final destination's code and data; compare the client-side and server-side approaches described in the issue.