We've got a quite large amount of mostly JCR-oriented actions, which would be nice to re-use.
The biggest blocker is that we don't normally use the JcrNodeAdapters anymore, and those are required by the majority of such actions.

Proposal: In case the new app operates with JCR nodes, whenever the action is executed, wrap the selection into a JCR node adapter and add it to the list of the context objects available to the action (i.e. pass to ComponentProvider#newInstance).

Acceptance criteria:

• Take inventory of current actions that need JcrNodeAdapters
• List actions that will continue to work without changes.
• For actions that require changes, propose how to provide compatibility.

Timebox analysis: 8 SP