created new object that acts as list but also retains metadata

[hwnjng]

In response to: #12.

Object extends list but also takes in metadata => Tackles issue of "I'd rather expect the metadata to be pertinent to the list of objects returned"

---

This change is 

[patrickdevivo]

@mmlb - @hwnjng is working on the fmt fixes to make drone happy

[mmlb]

So I think instead of having the caller deal with pagination somehow we should just handle it in the api. Have a count=-1 default param or something. If its None then fetch all the pages and return everything, otherwise return only count num. Leave per_page unset so api can be the decider or per_page.

This is much more useful to callers by default and leaves them the flexibility choose only some.

[patrickdevivo]

@mmlb totally agree, but we just wanted to keep the scope of this PR small for now just to make the metadata available to begin with, and then figure out how to "automate" the pagination. By API I assume you mean the outward facing interface of this SDK and not the Packet API?

[mmlb]

Thing is that if we do the automatic fetching then there's no need for this PR.

[mmlb]

🤔 not unless we want to keep this pr anyway in case the caller calls with a specific count, and we'd have this information for them to re fetch to pull it all in. Not really sure thats a useful case to consider though.