Take other relationships into account when computing visibility

## What problem does this solve or what need does it fill?

When attempting #21812, the root node cannot be a child of a non root node,cannot control the visibility settings of the root node based on non parent-child relationships.
Perhaps in the future, we need visibility control for non parent-child relationships?

## What solution would you like?

This will involve data competition for visibility,
At the same time, it is also necessary to handle the transfer of visibility from one relationship to another.

Perhaps we can create a table to control based on the weight of each relationship.

The issue names no files, tests, or entry points. Start by reading issue #21812 and tracing the existing visibility computation for parent-child relationships; the issue needs a decided model for competing relationship weights and visibility transfer before completion can be verified.

Written by the indexing model from the issue text.