Warnings lose need special handling for context

Problem/Motivation

Warnings that are created by 'warn' rules need a bit of special handling. If a warning is shown AND there was something like a 'prevent' that kept the content from saving, then the warning message has the context it needs because you are still on the same edit form. The problem is that if a warning is shown when the save is not prevented, then the warning appears for example when the site returns you to the content list, so the warning appears, but the user has no reference to what entity generated the warning.

Unfortunately when the warning message is generated, the code has no idea whether the save event is going to be allowed or not so it does not know to optionally include more context like a link to the node.

Steps to reproduce

Proposed resolution

Likely the only solution available to us it so include the link to the content in every warning so that wherever the warning appears, the user has the context and the ability to get back to fix the issue.

Remaining tasks

User interface changes

API changes

Data model changes