The following issue has to be addressed

• Definitions that are hot-fixed within resources-app are considered as config-based definitions => show file action broken

This happens due to a mis-understanding of how does the notion of configuration source correlates with ResourceOrigins and with JCR config and resources workspaces. The following logic should be used:

• Anything that is served via the ResourceOrigin (this includes JCR resources workspace) is treated as a file-based definition
• Anything that comes from JCR config workspace is treated as a JCR definition.

Luckily to simplify this - MAGNOLIA-6081 brings us a new simple API which allows to ask a DefinitionProvider - which config source it initially is coming from.

As a complement to this effort - we should re-purpose the Source column in the overview table - let it omit the information about the exact origin of the file-based definition (i.e. FS, classpath or resources workspace), they all are in the end are files.