fix: ordering of functionality for setting and evaluating label expressions

[juliev0]

Fixes #9625

Fixing the order of functionality for setting and evaluating label expressions, to address the issue that a LabelsFrom expression may be dependent on the evaluation of a parameter that it uses; as well as the issue that workflow.labels.x may be used somewhere else in the spec. The new order is:

1. Set globalParams and substitute them in the spec for everything except WorkflowMetadata.LabelsFrom expressions (which will be done in step 3)
2. Evaluate WorkflowMetadata.LabelsFrom expressions and set globalParams for those
3. Perform any substitution in the spec based on these new globalParams

[juliev0]

In this new test, we verify that:

1. workflowMetadata.labelsFrom.mutexName.expression (which is based on another parameter) gets evaluated correctly
2. the result of that label gets incorporated into spec.synchronization.mutex.name

[juliev0]

note this isn't new code - just relocated