fix short_names -> shortNames

[mindreframer]

problem:

• currently short names are completely ignored by k8s

solution:

• use camelcase. It looks a bit weird in Elixir, but works
• alternative would be to dynamically adjust casing on all field names in requests / responses and this might introduce own problems. imho: keep it KISS

[coryodaniel]

I think this kinda ties into #23 ... We could have a function in the Naming (or similar) module that snake_case <=> camelCase map keys. I assume this will start cropping up more and more as features are added. Might also be nice to auto snake_case HTTP responses and camelCase requests in #22.

Thoughts?

[mindreframer]

@coryodaniel I understand your arguments yet this can become a major yak shaving pit fall...

snake_case <=> camelCase conversion is not 100% reversible and will require some fancy rules / exceptions (all uppercase? URL ? ID? UUID) and all kinda little workarounds.... In theory nice, in practice it works 99% and bites you with weird bugs.

Maybe I'm overestimating the danger here, yet my gut feeling tells me to stick to most simplest approach possible.
And there are some a bit cooler things to implement than reliable key conversion snake_case <=> camelCase within k8s lingo. IMHO if we stick to Kubernetes wording / casing 100%, there is no need to explain or implement things.

Also I'm a bit in crunch mode, so i need working simple things fast ... 😅

[coryodaniel]

Valid point. We should keep this on the radar.

It’s looking especially difficult w annotations, since the let’s are often domain names - we’d probably need to skip annotations altogether.