Fix aware mutating attribute bag

[ganyicz]

The scenario

Blaze removes attributes defined in @aware from the attribute bag.

{{-- resources/views/components/input.blade.php --}}

@aware(['type'])

<input {{ $attributes }}>

Rendering <x-input type="number"> will produce:

• <input type="number"> in Blade
• <input > in Blaze

The component intentionally doesn't use @props to demonstrate the issue

The problem

When components are folded, they do not have access to the data stack which @aware uses. We compensate for that by appending parent attributes to the node during folding. For example, when folding <x-input> in the view below:

<x-wrapper type="number">
    <x-input> {{-- Uses @aware(['type']) --}}
</x-wrapper>

We take type="number" from the parent and add it to the node itself before rendering:

<x-input type="number">`

This provides the parent data to the component, however, it also adds type to the attribute bag. We then have to unset($attributes['type']) when compiling @aware, which causes the original issue.

This only affects a narrow use-case: if @props aren't used or if the attribute bag is accessed before @aware but it highlights a real divergence from Blade.

The solution

Provide parent data via data stack and stop mutating the attribute bag from inside @aware.

$awareData = Arr::map($renderable->parentAttributes, ...);
$attributes = Arr::map($renderable->attributes, ...);

$this->runtime->pushData($awareData);
$this->runtime->pushData($attributes);

require $compiled;

$this->runtime->popData();
$this->runtime->popData();

We've already had an isolated data stack, however we only pushed $attributes which only containes the data of the component that is currently rendered. Adding $awareData fixes the issue and the attribute bag can remain untouched.

This supersedes PR #200, which uncovered this issue.

[github-actions]

Benchmark Result: Default

Attempt	Blade	Blaze	Change
#1	246.87ms	15.21ms	93.8%
#2	239.72ms	15.38ms	93.6%
#3	242.08ms	15.21ms	93.7%
#4	240.49ms	15.25ms	93.7%
#5	241.73ms	15.19ms	93.7%
#6	239.97ms	15.51ms	93.5%
#7	242.58ms	15.44ms	93.6%
#8	244.28ms	15.26ms	93.8%
#9 *	242.60ms	15.83ms	93.5%
#10	245.60ms	15.25ms	93.8%
Snapshot	247.33ms	15.24ms	93.8%
Result	242.08ms (-2.1%)	15.25ms (~)	93.7% (~)

_{Median of 10 attempts (* = outlier, excluded from result), 5000 iterations x 10 rounds, 33.17s total}

_{To run a specific benchmark, comment /benchmark <name>
attributes, aware, class, default, forwarding, merge, named-slots, no-attributes, slot, compilation}

[ganyicz]

/benchmark aware

[github-actions]

Benchmark Result: Aware

Attempt	Blade	Blaze	Change
#1 *	552.68ms	36.60ms	93.4%
#2	562.27ms	37.48ms	93.3%
#3	555.90ms	37.52ms	93.3%
#4 *	542.80ms	38.25ms	93%
#5	559.25ms	37.75ms	93.2%
#6	551.64ms	37.53ms	93.2%
#7 *	551.15ms	38.51ms	93%
#8	552.35ms	37.46ms	93.2%
#9	557.14ms	37.65ms	93.2%
#10	557.13ms	37.37ms	93.3%
Snapshot	552.33ms	38.92ms	93%
Result	557.13ms (~)	37.52ms (-3.6%)	93.3% (+0.3%)

_{Median of 10 attempts (* = outlier, excluded from result), 5000 iterations x 10 rounds, 73.43s total}

_{To run a specific benchmark, comment /benchmark <name>
attributes, aware, class, default, forwarding, merge, named-slots, no-attributes, slot, compilation}