Fix compiled path overrides after Blaze runtime resolution

[prateekbhujel]

Fixes #177.

BlazeRuntime was caching view.compiled the first time compiledPath was read. In tenant setups that update the compiled view path after the runtime singleton has already been resolved, Blaze could keep compiling against the original cache directory instead of the tenant-scoped one.

This keeps the compiled path dynamic unless it is explicitly overridden, and makes sure the Blade compiler uses that current path before compiling a Blaze component.

[github-actions]

Benchmark Result: Default

Attempt	Blade	Blaze	Improvement
#1	382.86ms	16.03ms	95.8%
#2	379.65ms	16.27ms	95.7%
#3	377.36ms	16.09ms	95.7%
#4	386.63ms	15.95ms	95.9%
#5	377.50ms	15.76ms	95.8%
#6	384.17ms	16.00ms	95.8%
#7	377.76ms	15.97ms	95.8%
#8	383.40ms	16.09ms	95.8%
#9	384.13ms	16.09ms	95.8%
#10	377.39ms	15.92ms	95.8%
Snapshot	346.63ms	15.99ms	95.4%
Result	381.26ms (+10%)	16.02ms (~)	95.8% (+0.4%)

_{Median of 10 attempts, 5000 iterations x 10 rounds, 49.75s total}

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