✨ adding ability to get a APIReader from the client.

[shawn-hurley]

Adding a new interface APIClient to expose as part of the client
a non-caching reader interface.

fixes #180
fixes #245

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: shawn-hurley
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: droot

If they are not already assigned, you can assign the PR to them by writing /assign @droot in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[shawn-hurley]

I think this is probably the first step described in #180

I think the next step would be to talk about the return of the GetCache and/or change the name. I think we want the ability to get to the cache for adding event handlers and such, but maybe hiding/changing the reader interface? @droot thoughts?

[DirectXMan12]

I don't like this being part of client -- it brings weird implications to how we implement client. I think it should probably just be exposed directly on the manager.

[shawn-hurley]

I think that I agree with @DirectXMan12 I will close this PR and move this to the manager in a separate PR.