Add column sorting support to the Table component

[Oleg-Melnik]

This PR adds column sorting support to the table component, including sortable column definitions, sorting state management, and interactive table header behavior.

Below is an example of a typical usage scenario:

class UsersTable : Table<User>() {

    init {
        columns = listOf(
            TableColumn(
                name = "Name",
                sorting = TableColumnSorting(compareBy(User::name))
            ) { user ->
                Text(user.name)
            },
            TableColumn(
                name = "Created",
                sorting = TableColumnSorting(
                    comparator = compareBy(User::createdAt),
                    initialDirection = DESCENDING
                )
            ) { user ->
                Text(user.createdAt)
            }
        )
    }
}

[armiol]

@Oleg-Melnik please see some minor comments.

[armiol]

Let's make it a part of the documentation section, not a standalone comment. To me it looks like an implementation note.

[armiol]

Same as below.

[armiol]

Let's get rid of this paragraph altogether. If you read it, you may find it really tells nothing except "this is a software component that is designed as a class in OOP-style code".

[armiol]

Please kill this paragraph. It is obvious for humans. Not for agents, apparently.

[dpikhulya]

@Oleg-Melnik LGTM in general with a small potential improvement.

FYI: I've also created an issue that might be relevant in context of sorting or later if/when the table gets more column-related features: #125

[dpikhulya]

Maybe it would be nice if this defaultComparator also served as a fallback sorting direction even if column sorting is active — for the cases when any column comparator interprets items as equal. In this case this would be a second-level criterion that defines item sorting in such indefinite cases.

This could practically be useful when sorting by categorical columns (e.g. statuses, etc.), in which case many rows would turn out to be "equal" according to the column's comparator alone.

If it works that way already (I didn't check it), maybe just worth documenting it here for clarity.