Avoid folly::init overwirte log configuration.

[Shylock-Hg]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

Description:

Avoid folly::init overwirte the glog configuration.

How do you solve it?

Patch of #4409

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

• Unit test(positive and negative cases)
• Function test
• Performance test
• N/A

Affects:

• Documentation affected (Please add the label if documentation needs to be modified.)
• Incompatibility (If it breaks the compatibility, please describe it and add the label.）
• If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
• Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

[critical27]

Please verify if the behavior in the comment.

[Shylock-Hg]

In current folly::init and SetUpLogging is called after pid checking too.

[Shylock-Hg]

But Standalone daemon and Graphd daemon don't require this constraint even before this PR, need to modify it?

[critical27]

It is ok for now. I can't clearly remember why we move setupLogging very close to start position of the main.