Thor manager does not update jobId when running subsequent jobs in k8s
Description
When in lingering mode (default), the thor manager is not updating the jobId when the next job comes in, causing the jobId column to be populated by the 1st workunit that initiated the instance.
When in lingering mode (default), the thor manager is not updating the jobId when the next job comes in, causing the jobId column to be populated by the 1st workunit that initiated the instance.