chore: Refactor the method creating sync tasks

[thecooldrop]

Hello everyone, during my work on ArgoCD I noticed that quite a few methods in GitOps engine are quite large, and are not broken down into smaller, understandable methods. This has made it very hard for me to understand what the methods and functions do, as I had to keep very large information present in my mind, in order to understand them.

In this PR I have extracted blocks of code into hopefully more understandable, smaller methods and functions. For me the code is more readable now, because:

• I can understand each part independently from other part
• Names of methods provide some context as to what is being done
• Names of methods are more aligned with actual functionality provided, make it easier to create a connection between ArgoCD functionality and the code
• Less context pollution, because there is less variables present now

If this change is welcome I would like to do similar changes other methods as well.

Note that there are few other changes which could be done, but I felt that I would need to write additional tests to cover this behavior, which is currently out of scope for me, as I am both only vaguely familiar with Golang, and even less so with this codebase.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[thecooldrop]

Hello @jessesuen @alexmt , is there anything I can add to this PR that would ease the review process?