Handle missing compiled views during folded expiry checks

[prateekbhujel]

Fixes #175.

Blaze checks folded front matter after Blade reports a compiled view is fresh. If that compiled file is removed before Blaze reads it, the read can fail instead of letting Blade rebuild the view.

This retries through the compiler once when that compiled file is missing, then checks the fresh compiled output.

[github-actions]

Benchmark Result: Default

Attempt	Blade	Blaze	Improvement
#1	352.15ms	16.45ms	95.3%
#2	351.08ms	16.12ms	95.4%
#3 *	363.05ms	16.50ms	95.5%
#4	355.59ms	16.40ms	95.4%
#5	354.51ms	16.03ms	95.5%
#6	358.51ms	16.51ms	95.4%
#7	349.15ms	16.15ms	95.4%
#8	348.07ms	16.45ms	95.3%
#9	351.67ms	15.97ms	95.5%
#10	352.16ms	15.99ms	95.5%
Snapshot	355.34ms	16.27ms	95.4%
Result	352.15ms (~)	16.15ms (~)	95.4% (~)

_{Median of 10 attempts (* = outlier, excluded from result), 5000 iterations x 10 rounds, 46.61s 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}