Improve meta object exposure and pagination support

[oseovie]

While reviewing PayStackEase compared to Paystack’s official API documentation, I noticed the following:

1. meta object is not clearly exposed

Paystack API responses include a meta object containing pagination details (page, perPage, pageCount) and diagnostic information for failed requests.
PayStackEase methods like transactions.initialize() and transactions.list() currently return only the data portion of the response.
This makes it difficult for developers to access pagination info or debug details.

2. Pagination guidance is missing
   List endpoints often return multiple pages of results.
   The library does not provide helper functions or examples for handling paginated responses.
   Developers may struggle to retrieve all results without guidance.

Suggested improvements:
Update methods to optionally return the full API response including meta.
Add documentation and examples showing how to use meta for pagination and error debugging.