Guards are guarding previous route

[Vinzent03]

Describe the bug
When beaming via context.beamToNamed("") the guard runs on the previous url. So it doesn't catch a wrong beam.

Beamer version: v1.5.0

To Reproduce
Steps to reproduce the behavior:

1. Set Guard to run on /account
2. context.beamToNamed("/account")
3. context.beamToNamend("/account/password")

Expected behavior
Guard catches the first beam and runs its check.

Actual behavior
Guard catches the second beam and runs its check, because it now checks the uli from the first beam /account.

Smartphone

• Device: Xiaomi Mi 9 Lite
• OS: Android 11

Additional context
When downgrading to 1.4.0 the bug is gone without any other code changes.
I could track it down to https://github.com/slovnicki/beamer/blob/master/package/lib/src/beamer_delegate.dart#L406, where locationBuilder produced location's state has the wrong 'RouteInformation`.

[slovnicki]

Hey @Vinzent03 👋
Sorry for a late response, I've been super busy.
Now I've thoroughly looked at this and maybe figured it out.

Very curious; I started writing some test for all the cases and it seems to happen only when redirect route is the origin route (from where it is being beamed to the guarded route). I'm still not 100% sure but will try to fix this by the end of this week.