[5.x]: Matrix field conditions evaluated against block instead of parent entry

What happened?

Description

When adding conditions to fields within a matrix block, they often don't work as expected because the conditions are evaluated against the matrix block itself rather than the parent entry. In most cases, these conditions should be based on the parent entry, not the matrix block.

Example:
A matrix block contains an image field.
Set a condition to hide the image field if the parent entry's level equals 1 (level == 1).
The image field never shows because block.level is null.

Thoughts:
I understand why this happens — because everything in CraftCMS is considered an entry now, and entry types can also be used as a standalone section. In such cases, conditions work as expected. However, in the context of a matrix block within another entry, it would be more intuitive if the conditions evaluated the parent entry rather than the block itself. Ideally, the behavior should adapt based on how the entry type is being used, OR we need an aditional condition field "Entry Parent Condition".

Steps to reproduce

1. Create a matrix field.
2. Add a field to the matrix block and configure a condition based on the parent entry (e.g., level == 1).
3. Test to see if the field is shown or hidden as expected.

Craft CMS version

5.5.2

PHP version

8.2.24

Operating system and version

Linux 6.11.9-orbstack-00279-g4cf512143f2e

Database type and version

MySQL 8.0.36

Image driver and version

Imagick 3.7.0 (ImageMagick 6.9.11-60)

Installed plugins and versions

Reproduce the matrix-field condition case described in the issue using a parent entry level and a matrix block field. Start by tracing where conditions are evaluated for matrix blocks versus their parent entry; done means the documented parent-entry condition behaves as expected without breaking standalone entry-type conditions.