Initial stab at adding TSC support to task_proc

[nemacysts]

This should help Karpenter spread things out.

[ilkinmammadzada]

Why we need to create a local class since it exists in k8s lib?
I am asking because TSC will be changed in next(ish) release.
e.g. nodeAffinityPolicy, nodeTaintsPolicy, matchLabelKeys, minDomains

[nemacysts]

this is for the typing task_proc task_config data: we get data as dicts and then later translate them to k8s objects

[nemacysts]

I tested this with a local tron using with something like

                topology_spread_constraints=[
                    {
                        "max_skew": 1,
                        "topology_key": "topology.kubernetes.io/zone",
                        "when_unsatisfiable": "ScheduleAnyway",
                        "label_selector": {
                            "app.kubernetes.io/managed-by": "tron",
                        },
                    },
                ],

and pods were correctly spun up with

  topologySpreadConstraints:
  - labelSelector:
      matchLabels:
        app.kubernetes.io/managed-by: tron
    maxSkew: 1
    topologyKey: topology.kubernetes.io/zone
    whenUnsatisfiable: ScheduleAnyway

in their pod specs (and I saw pods launch across multiple AZs)