- we're going to need this extra specificity shortly for when we add internal context defaults

- I played around with it, but unfortunately it doesn't makse sense to define the defaults in the component itself still. You either run into dependency issues (if you try to import them) or you have a lot of extra `??` repeated code if you try to make an extra layer of fallbacks

…ults

- convert tests to RTL

- remove unnecessary `() => {}` callback default (since prop is not required), use optional chaining instead

- default props must be manually declared using jsdocs now, since react docgen can no longer use `=` fallbacks to figure them out

- note: setting `EuiTablePagination.defaultProps` unfortunately does not work, React will automatically populate them and they don't come in as undefined

- PaginationBar should not be testing props that are basic pass-throughs - EuiTablePagination should (the whole point of unit tests)
+ add test for PaginationBar logic that's actually there (onPageChange)

- Move said missing tests to EuiTablePagination and improve tests to use specific assertions instead of noisy snapshots

- to make it (maybe??) a bit clearer that component defaults in this context are 100% from the consumer and 0% from EUI at this point

via the magic of an inferred generic