Node ancestor publish state requirements unclear

Node ancestor publish state requirements unclear

## Gentics Mesh Version, operating system, or hardware.
0.35.0 running in docker-compose https://github.com/gentics/mesh-compose

## Operating System
MacOS 10.14.5

## Problems

### Mesh is inconsistent when returning error responses after nodes have been published which have unpublished parent nodes
#### Reproducer
**Scenario**: Node A has translation EN (unpublished). Node B has translation EN (unpublished) and has parent of Node A.
**Current behavior**: Publish Node B translation EN -> Node B translation EN is published without errors.
**Expected behavior**: Publish Node B translation EN -> Error response, because a published node should not have unpublished ancestor nodes.

### The concept of which node language should be required to be published in order to publish its child nodes appear to need more refinement
#### Example
**Scenario**: Node A has translation EN (published). Node B has translation EN (unpublished) and DE (unpublished) and has parent of Node A.
**Current behavior**: Publish Node B translation DE -> Node B translation DE is published without errors.
**Possibly desired behavior**: Error response, because Node A has no published translation DE (WebRoot).

Start by reproducing the Node A/Node B translation scenarios described in the issue with the Gentics Mesh 0.35.0 docker-compose setup. Verify the current publish responses, then clarify the intended ancestor-language rule before changing behavior; done means both scenarios have agreed outcomes and behave accordingly.

Written by the indexing model from the issue text.