feat(suite-native): Create generic picker header component

[jbazant]

Description

Introduce PickerHeader and PickerCloseButton components.

Related Issue

Resolve #16605

Screenshots:

[github-actions]

🚀 Expo preview is ready!

• Project → trezor-suite-preview
• Platforms → android, ios
• Scheme → trezorsuitelite
• Runtime Version → 23
• More info

Learn more about 𝝠 Expo Github Action

[vytick]

I have one small nit, but otherwise it is nice 👍

[vytick]

String is imo obsolete here, as the ReactNode can be string

[jbazant]

Fixed

[PeKne]

nit: You might want to use utility type RequireAllOrNone from type-fest library that we use in our repo (for example here).

Then you can remove isSearchInputVisible prop, because you can compute its values inside of this component based on the fact if any of the props were passed or not.

[jbazant]

You might want to use utility type RequireAllOrNone

I was unable to make it work with RequireAllOrNone. My goal was to define type

 {
    title: string | ReactNode;
    children?: ReactNode;
    isSearchInputVisible?: false;
} | {
    title: string | ReactNode;
    children?: ReactNode;
    isSearchInputVisible: true;
    onSearchInputChange: (value: string) => void;
    searchInputPlaceholder?: string;
    isSearchInputDisabled?: boolean;
    maxSearchInputLength?: number;
}

where only onSearchInputChange is required. Rest of the SearchInput props should be optional. To my understanding this is not possible with RequireAllOrNone or any other other utility from that library. I would be happy to learn that I am mistaken.

Also all those never types were defined just to simplify access to SearchInput props. I've updated that code a bit, please take a look whether you like it more.

Then you can remove isSearchInputVisible prop

I actually considered to remove this prop, but decided to left it there for better readability. Do you prefer to remove it and decide solely on presence of onSearchInputChange prop?

[PeKne]

Ok, keep it as it is. I did not realize that most of the props can be undefined in both cases and only onSearchInputChange is required while is the isSearchInputVisible set to true.

I'm happy with the latest version 👍.

[vytick]

/rebase

[github-actions]

Start rebasing: https://github.com/trezor/trezor-suite/actions/runs/13009497318