fix(landing-page): pass loginAlert action and translationParams

[ljanner]

Resolves #1555

---

• I confirm that this MR follows the contribution guidelines.

[gemini-code-assist]

Code Review

The pull request correctly implements the passing of action and translationParams from the loginAlert object to the si-inline-notification component. This aligns with the AlertConfig model and ensures that the notification can display actions and use translation parameters as intended. The changes are straightforward and resolve the described issue effectively.

[github-actions]

Documentation.
Examples.
Playwright report.

Coverage Reports:

• element-ng
• element-translate-ng

[dauriamarco]

Thank you @ljanner 👌 Could you also add an example for this and maybe an e2e to test it? In the si-landing-page-single-sign-on-login.ts for example:

  ngOnInit(): void {
    // note: this is normally in translation file, this is for demo proposes only
    this.translate.set('DEMO.CONFIRM_LOGIN_MSG', 'Hi {{user}}! You have logged in.');
  }

  ssoLogin(): void {
    this.loginAlert.set({
      severity: 'success',
      message: 'DEMO.CONFIRM_LOGIN_MSG',
      translationParams: { user: 'User' }
    });
  }

[ljanner]

Thank you @ljanner 👌 Could you also add an example for this and maybe an e2e to test it? In the si-landing-page-single-sign-on-login.ts for example: ...

Thanks for the really helpful snippet, added an e2e test 🙏

[dauriamarco]

LGTM 👍

[github-actions]