FIX: Fix a 6000.2 build automation instability

[K-Tone]

Description

While working on another case I noticed that sometimes our automation would fail if it happens to pick up a Unity beta version that hasn't yet finished being built apparently. To fix that, I was suggested to add a --wait flag everywhere 6.2 is used. That's precisely what happens here.

Testing status & QA

This only affects automations.

Overall Product Risks

• Complexity: Low
• Halo Effect: Low

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

After merge:

• Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.

[ekcoh]

Thanks for looking into this @K-Tone !

[windxu88]

LGTM