Add bundle with custom nodetypes using Sling-Initial-Content

### Expected Behaviour
I can add custom nodetypes that add extra functionality to for example `cq:Component`

### Actual Behaviour
Following exception is thrown: Content Package Converter Exception the following node types could not be registered because of unresolvable dependencies: {http://www.amplexor.com/jcr/ampx/1.0}VersionedComponent

### Reproduce Scenario (including but not limited to)
Have a bundle that registers some nodetypes:

versioned-components.cnd:
```

//-----------------------------------------------------------------------------
// Mixin node type to mark a cq:Component as versioned component
[ampx:VersionedComponent] > cq:Component
mixin

// Unversioned resource type that will be used in the content
- ampx:unversionedResourceType (string)

// Version when this specific component should become active
- ampx:introductionVersion (long)
```

```

org.apache.felix
maven-bundle-plugin
true



ampx=http://www.amplexor.com/jcr/ampx/1.0


SLING-INF/nodetypes/versioned-components.cnd





baseline

baseline

package

```

Add the bundle to your `all` package and see the exception.

Start by inspecting the Content Package Converter path that reports unresolvable node type dependencies, then compare it with the provided versioned-components.cnd and maven-bundle-plugin Sling-Nodetypes configuration. Reproduce the failure by adding the bundle to the all package; done means the custom ampx:VersionedComponent nodetype can be processed without the reported exception.

Written by the indexing model from the issue text.