Distinguish between Normal, Default and Overridden workflows in workflow_overview_all()

[inadarei]

When workflows are exportable they can be in one of the following three states:

• Normal - database-only
• Default - code-only
• Overridden - provided by code, but overridden in the database.

There are cases when operation titles have to be different depending on the state. One such very common case is for "edit" operation. In all existing exportable UIs, the edit link says "edit" if an object is Normal or Overridden, but says "Override" if the object is Default, allowing very important ability for users to identify objects that have not, yet, been overridden.

I am going to fix this in my fork by allowing links array to supply "title_default" which will be used instead of the "title" key, if object is in Default state.

Obviously, there could be a more generic case, allowing modules to also supply "title_normal" and "title_overridden". However, the only known and widespread case that we know of, right now, is the case of "Edit/Override", so I am avoiding preemptive complication of code, unless we see that it is necessary. Trying to keep it simple, for now.

[q0rban]

Makes sense to me. I will have a look at your code to check out your implementation