[Feature Request] Provide a reason string when marking a package dirty

eInterdependencies between the assets aren't always obvious, and sometimes are counter-intuitive (e.g. assigning a material to a new type of asset generally requires saving the material after a usage flag has been auto-set). Users routinely ignore them as saving and checking in assets that you didn't touch is scary, especially in a large project. We need to provide a user visible string that would explain why it is necessary.

Slack thread about this: [Link Removed]

[Link Removed] sketched the ideal UI for this, although IMO even something like a string next to each prompted asset would be an improvement.

[Link Removed]