Wrangler should warn when redirected config is out of date

[emily-shen]

Describe the solution

Sometimes i just want to redeploy with a small change to my wrangler file - e.g. changing an env var or changing some binding resource config. It is easy to forget that you need to rebuild with vite in order for the redirected config to pick up these changes, and i can imagine that it would be difficult for users to debug that the reason your config changes are missing is because you forgot to rebuild.

It would be helpful for wrangler to detect that your redirected config is not up to date and warn.

Issue courtesy of me spending an hour yesterday debugging how we diff container config :D

[petebacondarwin]

Tricky, since how would Wrangler know that the file generated by some arbitrary tool is out of date?
I think the only thing we could do is compare the timestamps on the source Wrangler config with the generated redirected one?