fix(user-onboarding): restore tour button actions

[piyushsinghgaur1]

Description

In @sourceloop/user-onboarding-client, the tour's Next, Previous and custom buttons (e.g. Skip) did nothing when clicked. This PR makes them work again.

How the bug came about

• shepherd.js expects a button's action to be the click handler itself ((this: Tour) => void) and calls it on click.
• TourButton.action was typed as () => Step.StepOptionsButton['action'], a function that returns a handler. While the actionAssignment parameters were untyped (any), this mismatch never caused a compile error.
• The stricter TypeScript 6 checks that came with the Angular 22 upgrade needed explicit types on those parameters. To match the TourButton.action type, the assignments were then wrapped as b.action = () => handler. On click, shepherd.js got the handler back but never ran it.

The fix

• models/tour-button.ts: type action as Step.StepOptionsButton['action'], which is what shepherd.js actually uses.
• lib/tour-service.service.ts (actionAssignment): assign the handlers directly again, as before the upgrade, for prevAction, nextAction and custom registered functions.
• user-onboarding-element/package.json: the element bundle hash, regenerated by the build.

No regression expected

• actionAssignment is the only place that sets action, so runtime behaviour matches what it was before the Angular 22 upgrade.
• The type change is compatible for apps: anything that assigns a handler to action still type-checks.
• Apps that added a local workaround for this (for example, patching actionAssignment to call the returned handler) can remove it after upgrading.

Fixes #87

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• ng build userOnboardingLib succeeds on Angular 22.2.0 / TypeScript 6.0.3.
• The built bundle assigns the handlers directly, and the published .d.ts has action?: Step.StepOptionsButton['action'].
• A standalone strict TypeScript 6 check compiles with the corrected type. The previous type still rejects a () => void handler.
• The pre-commit hook (lerna run test) passes.
• Manual check in a consuming app: Next / Previous / Skip in a multi-step tour, using a packed build (npm pack from projects/user-onboarding-lib/dist).

Checklist:

• Performed a self-review of my own code
• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• API Documentation in code was updated
• Any dependent changes have been merged and published in downstream modules

[Akanksha13-dev]

Screen.Recording.2026-09-28.at.5.05.25.PM.mov

working fine