Since the rendering host is the same host as the current request, there
is not need that it is part of the URL

(cherry picked from commit 0e2743a1)

(cherry picked from commit 70245ec1)

When the site runs in channel mgr, it can have the _cmsinternal path info
element. We need to account for this

When there is a rendering host querystring in the channel mngr, the
query string could have twice the ?

since the channelPath is not below hst:channels any more, the implementation
was wrong

Since hst:channels got removed, we should not test a path below
hst:channels any more

Since preview variants do not have a publication date, we should not sort
on that field. Sorting on the modification date for preview makes much
more sense

Sort order properties are something else than where clause constraints
so should not be mixed

If there is no component, for example for a rest request, just return
whether the sitemap item is configured to cache or not

I removed the second component and component interface test class. It was not needed: the different configurations for pickers per field must be available for tests. They can be in the same class.

It should be prepended by the pickerRootPath if that is given, otherwise the channel root path

HSTTWO-4247 make test data for picker root path absolute, as described in the javadoc of the JcrPath annotation

The html comment will now contain the information that the component is
locked when the channel is locked. The locked user will be 'system'.

PS or partners might be used to or have a script that removes -preview
configs during a new deployment, including preview configs of branches.
For master branches the -preview config is already created automatically
if it's missing, but for branch config not.

Solve this by also recreating -preview config of the branches whenever
master -preview config is recreated. The channel manager will call
startEdit for the master before it switches to a branch, so it's safe to
implement this in the MountResource#startEdit().

- only log warnings (errors should only be used when thing are badly
  broken and require sysadmin intervention)

- log the render path of the current template in the warning, so a
  developer can easier locate the manageContent tag in error.

- consistently use the phrase "manageContent tag"

If the tag attribute rootPath is not available and the @JcrPath annotation of the component parameter is not given, use the channel root path as fallback/default for the picker root path. This prevents that the picker dialog allows the user to pick documents from outside the channel's content folder.

In case this IS actuallly wanted, then the rootPath attribute could be configured with something like '/content/documents' to allow for this.

Due to the fact that now in many more cases the pickerRootPath by default is provided, a number of unit tests had to be extended to cover this.

Also renamed the following properties:
 - componentValue => parameterValue
 - componentParameterIsRelativePath => parameterValueIsRelativePath
 - componentPickerConfiguration => pickerConfiguration
 - componentPickerInitialPath => pickerInitialPath
 - componentPickerRemembersLastVisited => pickerRemembersLastVisited
 - componentPickerRootPath => pickerRootPath
 - componentPickerSelectableNodeTypes => pickerSelectableNodeTypes

 Removed 'hippoBean' from warning as it already mentions the term
 'handle' which is a well-known Hippo concept.