feat: Add ability to configure loglevel for each ArgoCD component

[tylerauerbeck]

What type of PR is this?

/kind enhancement

What does this PR do / why we need it:
This PR adds the ability to adjust the loglevel of each of the ArgoCD components (controller, repo, server)

Have you updated the necessary documentation?

• Documentation update is required by this PR.
• Documentation has been updated.

Which issue(s) this PR fixes:

Fixes #329

How to test changes / Special notes to the reviewer:

After building the operator from this PR branch, you can deploy it with the following to confirm the loglevel functionality:

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd
  labels:
    example: basic
spec: 
  server:
    logLevel: "warn"
  repo:
    logLevel: "error"
  controller:
    logLevel: "info"

If you don't set any of the above, it will default the loglevel to info (which is the current behavior of each of the components).

[CLAassistant]

All committers have signed the CLA.

[wtam2018]

It looks good. Just a few questions. Thanks.

[tylerauerbeck]

@wtam2018 Updated based on your requests. But I do see that it appears that the controller and server pods are entering CrashLoopBackOff. Going to take a look at this now.

[wtam2018]

Any chance we can add this set loglevel feature to applicationset-controller as well? :-)

[tylerauerbeck]

@wtam2018 Think I've got everything fixed up now. I've also included the loglevel for applicationset. Just waiting on the tests to pass now.

[tylerauerbeck]

@wtam2018 Looks like all is good here. Are there any other changes you wanted to see?

[wtam2018]

Thanks for updating. It looks good. Have a few minor suggestions. (note: indent is a bit off)

[tylerauerbeck]

@wtam2018 Thanks for the recommendations. Got all of those merged in and looks like tests have passed. Let me know if this is good to go.

[wtam2018]

Please re-generate CRD.

[tylerauerbeck]

Done.

[wtam2018]

LGTM
thanks @tylerauerbeck !