it most likely had bad limits set making it so we wouldn't be able to
run a job.

It turns out we need to send the update every time since there isn't a
super quick way to tell the association didn't change.

the bad test afterwards fails

and call it when the job state is read instead of in the middle of
a reconfig which may be too late as the priority plugin needs the arrays
set up when _sync_nodes_to_comp_job is called in slurmctld/read_config.c

to timeout

to timeout