'Update reason' message in UI should differentiate between dependency changed vs. config file changed

Describe the Feature You Want

The UI should make it clear when a resource updates because one of its dependencies changed vs. when its config changed due to a changed config file/Tiltfile re-execution.

Current Behavior

The UI doesn't differentiate between these cases, see e.g. this snapshot -- one resource changed because its definition was changed in the Tiltfile, and one resource changed because its deps include the Tiltfile, but each has the same explanation in the UI: 1 File Changed: [Tiltfile].

Why Do You Want This?

The current messaging is misleading -- I've wasted time trying to figure out how the Tiltfile made it into a resource's deps/build context only to figure out that Tilt actually meant "this resource's definition changed via an edit to the Tiltfile".

Additional context
Tiltfile for the above snapshot:

local_resource('depends-on-tiltfile', 'echo beep', deps='.')
local_resource('doesnt-depend-on-tiltfile', 'echo boop')

Reproduce the two cases described in the Tiltfile example and compare the UI's current update explanations with the linked snapshot. Trace where the UI formats the “1 File Changed: [Tiltfile]” message, then make the completed behavior distinguish a dependency change from a resource-definition change caused by Tiltfile re-execution.