Make kubectl get chunk size configurable

[simu]

Also reduce chunk size to 100 (from 500) by default to reduce kubectl memory usage when dumping resource kinds with large individual resources.

Checklist

• Keep pull requests small so they can be easily reviewed.
• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog

[simu]

Update: after some more testing it looks like for high object counts (maybe > 5k or > 10k) neither --chunk-size=100 nor the default --chunk-size=500 return all objects when executing kubectl get -A <resource> with the corresponding chunk size flag. I haven't found any particularly relevant bug reports yet, and am still investigating.

[simu]

Update: after some more testing it looks like for high object counts (maybe > 5k or > 10k) neither --chunk-size=100 nor the default --chunk-size=500 return all objects when executing kubectl get -A <resource> with the corresponding chunk size flag. I haven't found any particularly relevant bug reports yet, and am still investigating.

Follow-up: Looks like pagination is only broken for resources managed by the openshift-apiserver, not sure how/if we want to proceed here.

[bastjan]

Implemented in #49