Allow opt-out to PodMonitor duplicate case-clashes

[clux]

Running kopium on the PodMonitor prometheus crd we encounter the strange enum that has two variants (with different cases) that by default produces this:

#[derive(Serialize, Deserialize, Clone, Debug, JsonSchema)]
pub enum PodMonitorPodMetricsEndpointsMetricRelabelingsAction {
    #[serde(rename = "replace")]
    Replace,
    Replace,
    #[serde(rename = "keep")]
    Keep,
    Keep,
    /// .....
}

we can now pass a substring of struct names to opt-out the rename behaviour so that if we run kopium here on podmonitors with:

  kubectl apply --server-side -f podmonitor.crd.yaml
  kopium --no-rename RelabelingsAction podmonitors.monitoring.coreos.com

we end up with a dumber enum that looks like:

#[derive(Serialize, Deserialize, Clone, Debug)]
pub enum PodMonitorPodMetricsEndpointsRelabelingsAction {
    replace,
    Replace,
    keep,
    Keep,
    drop,
    Drop,
    /// ...
}

of course, this will cause rust warnings for non_camel_case_types that will have to be ignored.

[clux]

some counterpoints to this;

• the generated output is awkward (due to the case ignore)
• it requires users to explicitly pass a complicated path and the fix is not super discoverable (not sure if there are good places to make suggestions)
• it won't fix ALL cases where the original case is invalid in rust ($action and action in the policy from comment)
• semi-complex interplay between the analyzer and the output module

[clux]

..maybe it is better to look for duplicate keys on the Container side (as per comment) and if we find any duplicates, THEN remove duplicates instead.. EDIT: trying this in #206

[clux]

After examining approaches, this PR here would force a hard-to-discover user opt-in to an inferior solution (with warnings generated) that would likely need further massaging on the user side to be nice.

Closing this in favour of #206 which is actually usable by default despite sometimes producing anachronistic member names.