Upgrade Angular to v19, add standalone

[alisaduncan]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Adding Tests
• Build related changes
• CI related changes
• Documentation changes
• Other... Please describe: Upgrade deps and convert to standalone

What is the current behavior?

Okta Angular uses an unmaintained version of Angular and doesn't support modern constructs like standalone.

Issue Number:
#151

What is the new behavior?

Angular v19 is minium required version. v19 is currently still in LTS.

Standalone, new provideOktaAuth() feature provider function, functional guards, has-any-group directive uses signal inputs so v19 is a min requirement now.

Does this PR introduce a breaking change?

• Yes
• No

NgModules is not supported out of the box with this change. The future of Angular is standalone.

old code:

@NgModules({
   imports: [
    // other imports
    OktaAuthModule.forRoot({oktaAuth})
  ]
})

new behavior:

const appConfig = {
  providers: [
    // other providers
    provideOktaAuth(withOktaConfig({ oktaAuth}))
  ]
};

In routes, migrate from canActivate: [OktaAuthGuard] to canActivate: [canActivateAuthGuard] in routes definition.

Other information

All test apps are standalone. v19 uses zone.js and default change detection strategy, v20 uses zoneless.

Reviewers