Job Tags not loading correctly in GUI

Current Behavior:

The GUI fails to load tags individually for each job and instead, only loads tags for the first job. When tags (including tag groups) are assigned to the first job, they persist across subsequent jobs. 
Additionally, if the job is clicked multiple times, an error message appears indicating that the jobName property is missing in the REST API call.

Steps to Reproduce:

• In a workflow, create two jobs
• Assign 2 tags to the first job (one of which includes a tag group).
• Click to navigate to the next job.
• Notice that the same tags from the first job are still applied to the second job.
• After multiple clicks, an error message is triggered, stating that the jobName property is missing in the REST API call.

Desired Behavior:

The GUI should load tags individually for each job, ensuring that each job displays its own set of tags accurately. Clicking on a job multiple times should not trigger any error messages. The jobName property must be correctly included in the REST API calls to prevent any errors.