select should always use object internally (remove sometimes array logic)

[EdJoPaTo]

Currently options of the .select() can be an Object or an Array (or a Function returning one of them).
This creates multiple cases internally.

Add a text: (key: string): string as additionalArgs. This defaults to key => key. When options is not an object, create one with text. This will simplify following logic.

[EdJoPaTo]

Alternatively remove Object completely and only allow text and the key[]. This is easy to understand for the user and most cases can be done with this.

Issue I can think of currently: button text is influenced by the whole array. Then the user logic has to check on it every call. This might be time consuming. The object would do this only once. But: Multiple pages of items could only change the current page of button texts.
Possibly helpful with this might me an additional argument for the text function: text: (ctx, key, arr: key[]): string

[EdJoPaTo]

solution implemented within the typescript rework: textFunc is available while the key array and the Object are still staying.

This allows for more dynamic usage. Internal logic is done with key[] and textFunc.