Refactor Part II: Split DuneClient Class

[bh2smith]

We split the DuneClient class up with an inheritance structure described vaguely as follows:

    Inheritance Hierarchy sketched as follows:

    DuneClient
        |
        |--- QueryAPI(BaseRouter)
        |       - Contains CRUD Operations on Queries
        |
        |--- ExtendedAPI
                | - Contains compositions of execution methods like `run_query` (formerly refresh)
                |
                |--- ExecutionAPI(BaseRouter)
                        - Contains query execution methods.

Note that this is based on #64 (which should be merged first).

Closes #69

cc @TheEdgeOfRage & @diegoximenes for additional review.

[bh2smith]

Note that we can circle back and clean this up even more later. This is mostly just an initial proposal for the final structure and servers as a starting point from which we can move things around as we see fit.

[msf]

Almost a SHIP IP, but see my suggestions and comments, they're tiny and fast to address (mostly about comments and moving functions up/down the file)

[bh2smith]

Just passed through your comments. Will address all the ones with thumbs up ASAP.

[RichardKeo]

Thanks for your work @bh2smith. I only did a quick pass and it looks good to me. I left a few comments, but they are nitpicks for the most part. Feel free to ignore them if you disagree.

[bh2smith]

Thanks @RichardKeo for your careful review. I will create relevant issues and make suggested changes here accordingly first thing tomorrow!

[bh2smith]

Okie, I have addressed all the comments and suggestions here (@RichardKeo). Please let me know if this is ready for 🚢 . Everything else will follow much easier from here (as everything is currently based on this branch).

[RichardKeo]

Looks good to me! 👍

[RichardKeo]

Are you still planning to add ping_frequency here?

[bh2smith]

In light of the backlog depending on this and all the comments addressed, I will merge this now. We can always double back and make additional changes upon request.