PascalCase conversion on structs in codegen

[clux]

Prost also converts aggressive PascalACRONYMCase names (with allcaps somewhere inside) like APIService to ApiService.
In general, this is a good improvement to the rust conventions, but, like #2, it has some problems:

1. have to disambiguate / break names used in kube

• ApiResource is an abstraction for APIResource in discovery/core
• ApiGroup similarly similarly for APIGroup in discovery

2. we break even further from official names

it's already a bit awkward that we convert their camelCased variable names to snake_case, this will also break some of the main structs.

---

personally, i don't really think 2. is a problem (everyone has been happy with the snake_case conversion in in k8s-openapi despite my earlier reservations), and this extra change only affects a small amount of structs who uses a decidedly bad naming convention.

[clux]

As an update, here's the small list of overrides currently:

k8s-pb/k8s-pb-codegen/src/main.rs

Lines 198 to 227 in 0111958

	let spec = spec
	.replace("APIService", "ApiService")
	.replace("CSIDriver", "CsiDriver")
	.replace("ClusterCIDR", "ClusterCidr")
	.replace("ServiceCIDR", "ServiceCidr")
	.replace("IPAddress", "IpAddress")
	.replace("CSINode", "CsiNode");
	let spec = spec.split("::").map(|m| format_ident!("{}", m));
	quote! {
	#tokens
	impl crate::HasSpec for #type_name {
	type Spec = crate::#(#spec)::*;
	fn spec(&self) -> Option<&<Self as crate::HasSpec>::Spec> {
	self.spec.as_ref()
	}
	fn spec_mut(&mut self) -> Option<&mut<Self as crate::HasSpec>::Spec> {
	self.spec.as_mut()
	}
	}
	}
	} else {
	tokens
	};
	let tokens = if let Some(status) = &resource.status {
	// HACK Prost changes message name `APIService` to `ApiService`, and `transformed.json` uses the original name.
	let status = status
	.replace("APIService", "ApiService")
	.replace("ServiceCIDR", "ServiceCidr");

This is clearly not a big problem. The only actual question here is what to do about ApiResource and ApiResourceList interface in kube later, and that can be solved there by use k8s-pb::ApiResource as pbApiResource and possibly some features around discovery and the struct source (which we will likely need anyway).

Closing this as wontfix.

[clux]

Have undone this in #49 because it would be somewhat annoying to have to keep track of these names upstream in the event of a swithover.