Now, that we use action availability, we inject AvailabilityCheckerImpl which in turn injects the DefaultContentConnector.

• The AvailabilityCheckerImpl is more targeted towards content-apps and has at least some JCR-specifics, which do not make sense in the pulse-context.
• The DefaultContentConnector is really a null-implementation and not a default one.
  It would make sense to resurrect the DefaultAvailabilityChecker and use that one. ContentConnector is not really needed I guess?