Run YarnUpdate only once for a version requirement

[AlekhyaYalla]

Issue: #4288

Currently, For a mono repo, when UpdateDependencyFiles is called for generating the lock file content, dependencies param is passed to it. Dependencies param contains the dep that needs to be updated in all required workspaces in the repo.

As far as observed, the multiple package.json (multiple requirements) for a dependency are getting passed for a mono repo., where it does have only a single yarn.lock file.
In this case, it's not necessary to run yarn update for each and every package.json or requirement if all are referring to same version.
For a single version, if run once, yarn.lock would be generated, and running the same version yarn update would result in repetition of the task.
In case if each package.json is referring to different versions of that dependency, this code would handle that by running yarn update accordingly.

[jurre]

Thanks @AlekhyaYalla, could you add some context on what this change does and how it works exactly?

Is there any additional test coverage that you think we could introduce around this?

[AlekhyaYalla]

Thanks @AlekhyaYalla, could you add some context on what this change does and how it works exactly?

@jurre Updated the description of the PR. My bad I missed it earlier. I hope the description is setting some context about the fix

Is there any additional test coverage that you think we could introduce around this?

Yes, I will add additional unit test cases for this change.

[AlekhyaYalla]

@jurre Could you please review this change and suggest if any changes are required on this?