Refactor Connection types with codegen

[rocktavious]

Resolves #

Problem

The connection types in our API are not generated by client-gen and thus everything for them in opslevel-go is hand crafted.

Solution

Actually generate the most common connection types that use nodes (for now excluding ones that truly need edges) and then fix up any none standard code because of this unification

Additionally I took the time to bite off the change to stop using totalCount everywhere since its unreliable between different queries (especially ones with filtering on the "list" call) So this just calculates on the client side the final total based on the final length of the nodes array after all pagination (and nested pagination) is done.

Checklist

• I have run this code, and it appears to resolve the stated issue.
• This PR does not reduce total test coverage
• This PR has no user interface changes or has already received approval from product management to change the interface.
• Does this change require a Terraform schema change?
  • If so what is the ticket or PR #
• Make a changie entry that explains the customer facing outcome of this change

[rocktavious]

This is the only customer facing change and since its a argument change in a type safe language customers code (or our other tools) will detect it at compile time