Introduced asyncAuthGuard and asyncAbpOAuthGuard to enable asynchronous authentication checks, particularly for OAuth flows involving code exchange. Updated app routes and OAuth module provider to use the new async guards where appropriate.

Description

Resolves #23286 (write the related issue number if available)

TODO: Describe what this PR has changed, add screenshot or animated GIF if available, write if it is a breaking change, and how to fix the breaking changes for existing applications if so.

Checklist

• I fully tested it as developer / designer and created unit / integration tests
• I documented it (or no need to document or I will create a separate documentation issue)

How to test it?

He describe in #23286

After setting up the environment for dev-app, you can start the application by running the following command in the npm/ng-packs directory:
yarn start

To reproduce the issue, add the canActivate guard to the home route in npm/ng-packs/apps/dev-app/src/app/app.routes.ts like this:

{
  path: '',
  pathMatch: 'full',
  loadComponent: () => import('./home/home.component').then(m => m.HomeComponent),
  canActivate: [AuthGuard]
}

Then, try to access the homepage after logging in — the issue (infinite redirect loop) will occur.

To fix the issue, replace AuthGuard with asyncAuthGuard.