Fix the ktlint failures already present on develop

[StylianosGakis]

Makes develop green just to make the rest of the stack cleaner

🤖 AI description:

Bottom of stack #3125. Independent of the rest of it in content, but it comes first deliberately: the layers above add a new ktlint rule, and this makes ktlintCheck actually pass so that rule can be trusted.

Why

./gradlew ktlintCheck fails on develop today, in two modules, with 37 errors unrelated to any in-flight work:

Rule	Count
standard:indent	27
standard:function-signature	4
standard:multiline-if-else	2
standard:max-line-length	2
standard:if-else-wrapping	2

Left alone it is a trap. Any PR that touches ktlint config looks like it broke CI when it didn't, which is exactly the situation the PRs above this one were in.

What changed

YourInfoTab.kt is purely ./gradlew :feature-insurances:formatKotlin output. Ignoring whitespace it is an if/else given braces and a newline, plus a function signature collapsed onto one line. No behaviour change.

TerminationRedirectionDestination.kt needed a manual fix, since standard:max-line-length is not auto-fixable. The same 127 character description string appears in two previews and is now split across two literals.

Verification

• Repo-wide ./gradlew ktlintCheck on this branch: BUILD SUCCESSFUL, 0 errors (down from 37).
• :feature-insurances:compileReleaseKotlin and :feature-terminate-insurance:compileReleaseKotlin both succeed.
• Verified again from the top of the stack: ktlintCheck reports 0 errors there too, so the new hedvig:namespace-import rule is being judged against a genuinely clean tree.

This commit was regenerated directly on current develop rather than rebased. Its entire content is formatKotlin output plus the one manual line split, so regenerating is exact and avoids resolving formatting conflicts by hand.