[pagination] support ellipsis

[jer3m01]

Describe The Problem To Be Solved

Fixed size pagination example from kb is best reference:
https://kobalte.dev/docs/core/components/pagination#fixed-items-example

The elements shown have to dynamically adjust for a consistent interface. Show page numbers when current page is close, show ellipsis when far.
Note: Kobalte uses siblingCount={1} instead of maxPages={7}, maybe consider using the same? (and remove maxPages)

Suggest A Solution

Add 2 props:

type PaginationOptions = {
	/** the number of pages to show at the same time around the current page */
	siblingCount?: number; // replaces maxPages
	...
	/** show an element between current page and first/last */
	showEllipsis?: boolean | ((page: number, pages: number) => boolean);
	...
	/** content for the ellipsis element, e.g. an SVG icon, default is "…" */
	ellipsisContent?: JSX.Element;
	...
}

const [paginationProps, page, setPage] =  createPagination({ pages: 10, ellipsis: true });

// works the same
<For each={paginationProps()}>{props => <button {...props} />}</For>

[atk]

I am against unnecessary breaking changes, even more if they introduce ambiguity - are previous/next counted as siblings or not. I'll look into adding epilepsie, though.

[davedbase]

I am against unnecessary breaking changes. I'll look into adding epilepsie, though.

For the 2.0 work I'm not as concerned about breaking changes tbh.

I do think this would be helpful to Kobalte since that's a tricky problem to solve.

[atk]

I find the team siblingCount still more ambiguous than maxPages. If I had to weight the improvement of conforming to another unrelated lib's naming against that drawback, I am still against changing the name. Kobalte is also releasing a new major version? Why aren't they changing their option then?