Steps to reproduce

1. Children pages nodes have been published without requesting it, the parent page was published via publish-workflow with recursive as false, and a task was created and approved, however the execution have published the complete tree.
2.  In the publishing log monitor, it can be observed that the parent was published and subsequently children pages were also published, however the children pages were published under the superuser not the user who published.
3. By keeping the Linked resources publication as reviewForExtendedPublication makes every children pages to be publish along with the parent, does not matter if there are common resources or not.
4. Create a new page without any content, kept it unpublished, published the parent as not recursive, after some minutes the new page also got published.
5. After setting the workflow config back to reviewForPublication, the problem does not happens anymore.

.. Logs, screenshots, gifs...

Expected results

• Having an option for the user to choose to automatically publish children pages and stop this automatically publishing function in the children pages if they have no content relationship to parent (eventhough naturally they are children pages, which should have at least one relationship in its hierarchy path).

.. Justify non-trivial expectations with a link to a doc or a relevant discussion.

Actual results

• See above

  Workaround

• N/A

Development notes

• N/A