[bug] Running field of TaskGroupScaleStatus doesn't get populated

[jrasell]

Nomad version

Nomad v0.11.2-dev

Currently the Running field of structs.JobScaleStatus is never populated when hydrating the response unlike other fields. Do we need this field, and if so, what should be used to populate it? If we do not need the field it should be removed from the internal struct and API response object.

[cgbaker]

going to add on to this bug: when the job is scaled to zero, nomad does not create a deployment. therefore, the current code is reporting invalid information by using the latest deployment, which refers to a previous version of the job. this should be corrected.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.