WIP: [NX-715] Query over components and assets

https://issues.sonatype.org/browse/NX-715

just some food for thought at this stage. not set on this, but my initial inclination was to have it return Asset objects for asset queries, and any kind of object for component queries. So you could have a list of MavenComponent objects come back, for example, if that's what you're searching for. Clearly it assumes that a Record-to-DomainObject capability exists somewhere under the hood. And if we go that way, a DomainObject-to-Record mapping would be good too. Similar in spirit to the Orient entityAdapters that have been done.
Would it be better to have `delete(ComponentId componentId, String path);` to align this with the other methods? (Also avoids the need for clients who have a component and path to first `get` the asset before deleting it.)