Adding idempotent label to Tron pods - TRON-2154

[EmanElsaban]

This PR adds a new field in soaconfigs for "idempotent", which will help us identify which Tron actions are idempotent vs which ones are not. It also creates a pod label with its value

Testing

Label set to true for test_load_foo1 job that has it set in soaconfigs

 (py38-linux) emanelsabban@dev208-uswest1adevc:~/pg/paasta$ kubectl-eks-infrastage -n tron describe pod/compute-infra-test-service.test--load--foo1.4837.foo.p42zob
INFO: You are using an Okta authenticated kubectl wrapper
Name:             compute-infra-test-service.test--load--foo1.4837.foo.p42zob
Namespace:        tron
Priority:         0
Service Account:  default
Node:             ip-10-40-16-118.us-west-1.compute.internal/10.40.16.118
Start Time:       Fri, 30 May 2025 14:09:17 -0700
Labels:           app.kubernetes.io/managed-by=tron
                  paasta.yelp.com/cluster=infrastage
                  paasta.yelp.com/instance=test_load_foo1.foo
                  paasta.yelp.com/pool=default
                  paasta.yelp.com/service=compute-infra-test-service
                  tron.yelp.com/idempotent-action=true
                  ...

Label set to false for other jobs that dont add idempotent key in soaconfigs

(py38-linux) emanelsabban@dev208-uswest1adevc:~/pg/paasta$ kubectl-eks-infrastage -n tron describe pod/paasta-contract-monitor.k8s.2468.sleep.2cujrz
INFO: You are using an Okta authenticated kubectl wrapper
Name:             paasta-contract-monitor.k8s.2468.sleep.2cujrz
Namespace:        tron
Priority:         0
Service Account:  paasta--arn-aws-iam-528741615426-role-paasta-contract-monitor-eks
Node:             ip-10-40-11-250.us-west-1.compute.internal/10.40.11.250
Start Time:       Fri, 30 May 2025 14:10:00 -0700
Labels:           app.kubernetes.io/managed-by=tron
                  paasta.yelp.com/cluster=infrastage
                  paasta.yelp.com/instance=k8s.sleep
                  paasta.yelp.com/pool=default
                  paasta.yelp.com/service=paasta-contract-monitor
                  tron.yelp.com/idempotent-action=false
                  ...

[nemacysts]

hmm, i'm not sure if we should document this flag in the paasta RTD or the tron one - https://paasta.readthedocs.io/en/latest/yelpsoa_configs.html#tron-clustername-yaml mentions that we only document paasta-specific stuff...but then we document some tron-only stuff anyway :p

that said: this generally looks good to me - although i'd prefer if more folks from the team would chime in on your proposal doc to make sure we're not just unilaterally picking what we want to do :p

[nemacysts]

feel free to drop:

Suggested change

	"$comment": "This will be used to determine whether the action can be retried without side effects."
	"$comment": If true, this action can be safely retried multiple times without unwanted side-effects."

[nemacysts]

i'd personally prefer

Suggested change

	"tron.yelp.com/idempotent-action": str(
	"tron.yelp.com/is-idempontent": str(

...but i also can't really justify why, so up to you :)