Timebox: 2 days
After this timebox, we should have at least follow up stories.
Additionally it would be good to have an understanding of how we can actually implement it with validated corner cases.

With MAGNOLIA-6128 and MAGNOLIA-6214, FreeMarker templates are now loaded from the Resources API and thus the resources workspace. Somehow we did not "finish" everything in this regard.

If one upgrades to 5.4, and freemarker config wasn't customized, templates will be loaded solely via resources API - so it's pretty confusing to have an app that lets one edit the"templates" workspace, but never gets used.

I'd suggest the inplace-templating module is now unnecessary:

• We should migrate templates that were copied/installed/edited in the templates workspace (only if modified or it they're "enabled")
• Remove workspace? We will not remove the workspace! Also see https://wiki.magnolia-cms.com/display/PDNOTES/Processed+resources%2C+template+migration+and+the+enabled+flag
• The resources App should allow creating folders and files (see MGNLRES-196, MGNLRES-186)
• Remove usages of install tasks which copies templates from classpath to workspace (it's used at least in stk/theme) (see MGNLRES-220)

This issue obviously needs to be replicated in MGNLINTEMPL; issues from MGNLINTEMPL might need to be moved to MGNLRES (some are probably redundant)