feat(auth-guard): add support for specifying a string to redirect to

[EdricChan03]

Closes #2287
Closes #2144

Checklist

• Issue number for this PR: feat(redirectUnauthorizedTo): allow passing query parameters #2287, Feature Request: Add queryParams into return url from custom AuthGuardPipe #2144
• Docs included?: no
• Test units included?: no
• In a clean directory, yarn install, yarn test run successfully? (yes/no; required)

Description

This PR introduces the ability to specify a UrlTree or a string to the return value of an AuthPipe and includes this feature in the existing redirect*To methods.

Previously, as noted in #2287, it was not possible to specify additional extras that could be passed to Router#createUrlTree.

Code sample

• With a string:

  export const redirectUnauthorizedToLogin = (afterLoginRedirect: string) => redirectUnauthorizedTo(`/login?redirectTo=${afterLoginRedirect}`);
  // ...
  const routes: Route[] = [
    {
      path: 'items',
      component: ItemsComponent
      ...canActivate(redirectUnauthorizedToLogin('/items'))
    }
  ]

• With a UrlTree (not currently possible atm):

  // TODO

[EdricChan03]

Seems that I did not think through the UrlTree portion - how should this be implemented?

EDIT: I've temporarily removed support for specifying a UrlTree

[EdricChan03]

/cc @jamesdaniels Thoughts? It's been about a month now

[NothingEverHappens]

Can we have a test for this new functionality?

[EdricChan03]

The current tests don't seem to test much... I'll see what I can do.

[NothingEverHappens]

Note: those suggestions would be relevant once @jamesdaniels confirms the feasibility of this approach

[EdricChan03]

I can't seem to rebase the changes - was the file updated in a recent commit?

[NothingEverHappens]

I can't seem to rebase the changes - was the file updated in a recent commit?
Yes, lots of style fixes across the codebase, may have to merge manually

[EdricChan03]

I can't seem to rebase the changes - was the file updated in a recent commit?
Yes, lots of style fixes across the codebase, may have to merge manually

I've just fixed the conflicts locally.

[jamesdaniels]

I'm good with this approach, UrlTree support would be great.

[EdricChan03]

I'm good with this approach, UrlTree support would be great.

I don't see any way for the user to pass in a UrlTree to the auth guard?