limited both scheduler to 1 CPU fix

all of

• cpu_count
• cpu_percent
• cpu_shares
• cpu_period
• cpu_quota

seems brittle, heavily dependent on the version and engine and in the end does not limit the resources.

i changed to cpus which seems somewhat stable. I also set the two sheduler to one cpu fix for now. if this become a bottleneck we can loosen the limit.

.env.example

@@ -223,9 +223,6 @@ TOMCAT_PROXY_URL=${PROXY_URL}/sta/
 SCHEDULER_IMAGE_TAG=latest
 # This is used in the Dockerfile of basic-demo-scheduler
 EXTRACTOR_IMAGE_TAG=latest
-# Adjust to your local machine [max: CPUS-1]
-SCHEDULER_CPU_COUNT=2
-
 
 ############################################################
 # cron-scheduler (debian, python)