Class "Arr" not found from ParentResolver when using it's functions

[Spice-King]

Describe the bug
ParentResolver assumes an alias for Arr exists, which if a project was created on an old enough version of Laravel (ours was on 5.5 over 6 years ago) might not be defined, or worse yet, pointed to something other than Illuminate\Support\Facades\Arr.

Yes, our config predates the use of Facade::defaultAliases(). Yes, I'm going to sit down and allocate time to update all the configs in this project I've inherited from my predecessor as they've been largely untouched, other than new custom additions and new package configs to it, in the past 6 years. No, despite me updating our configs, it should still be fixed here to avoid other people having issues if they alias Arr to something else. Yes, I do feel silly for finding this because of old configs.

What version does this affect?

• Laravel Version: N/A? But 10.17.0 currently, originally started on 5.5.19
• Package Version: 1.7.0, as far back as 1.1.0

To Reproduce
Steps to reproduce the behavior:

1. Remove alias for Arr from the app.aliases config array.
2. Define a breadcrumb that requires a parent resolver.
3. Load view for route that requires that breadcrumb.

Expected behavior
No error.

Additional context

Bug added in b678d0e. Trivial PR inbound.