Accurate sizes: Add ancestor block context

[mukeshpanchal27]

Summary

This PR add the ancestor block context for image and cover block that help to calculation of img sizes attributes.

See #1511

The context for ancestor block after the PR.

Group > Image

Array(
    [0] => Array( [core/columns] => default ),
)

Columns > Column > Image

Array(
    [0] => Array( [core/columns] => default ),
    [1] => Array( [core/column] => 100%)
)

Group > Columns > Column ( 50% ) > Image

Array(
    [0] => Array( [core/group] => default ),
    [1] => Array( [core/columns] => default ),
    [2] => Array( [core/column] => 50%)
)

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 10 lines in your changes missing coverage. Please review.

Please upload report for BASE (feature/1511-incorporate-layout-constraints-from-ancestors@3671902). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
...ns/auto-sizes/includes/improve-calculate-sizes.php	68.96%	9 Missing ⚠️
plugins/auto-sizes/hooks.php	0.00%	1 Missing ⚠️

Additional details and impacted files

@@                                      Coverage Diff                                      @@
##             feature/1511-incorporate-layout-constraints-from-ancestors    #1795   +/-   ##
=============================================================================================
  Coverage                                                              ?   57.53%           
=============================================================================================
  Files                                                                 ?       84           
  Lines                                                                 ?     6544           
  Branches                                                              ?        0           
=============================================================================================
  Hits                                                                  ?     3765           
  Misses                                                                ?     2779           
  Partials                                                              ?        0           

Flag	Coverage Δ
multisite	57.53% <66.66%> (?)
single	34.65% <66.66%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[joemcgill]

Thanks for getting this going @mukeshpanchal27. I can see where you're going but think that this introduces competing approaches to solving the same problem.

In #1701 we introduced the concept of max_alignment context, which is meant to be a way for ancestor blocks to share information about their alignment to inner blocks to use during rendering.

This approach is doing something similar by storing an array of the ancestor block hierarchy and their widths in a nested array that blocks can use during rendering.

Both have merits, but we should probably consolidate on one or the other approach and not both. In order to avoid passing a full array of block_width_data values to blocks that have to be looped through, we probably need to update the logic in auto_sizes_filter_render_block_context() that sets max_alignment context so that the alignment of a nested container block doesn't increase the max_alignment value.

For example, if you have a block structure like this:

group (align: 'default') > group (align: 'full') > image

The max_alignment context value should be 'default' since both the second group block and the image block will both be constrained by the max width of the first group block. However, we didn't consider nested blocks in the original implementation, so currently the max_alignment passed to the image will be 'full', resulting in an incorrect sizes value.

By handling nested alignment values with by keeping the max_alignment value updated we can avoid the need to pass the full array of nested block alignment values to the image block for it to loop through, like you're doing in #1818.

I do like the way you're calculating column widths by passing column_count context, but am think we might want to keep that context and container alignment width separate. What do you think?