[BUG] 使用全局viper进行yaml解析，会出现并发读写map的fatal error

[erberry]

为什么使用了一个全局的viper对象对yaml进行解析，viper不是并发安全的。

https://github.com/apolloconfig/agollo/blob/v4.4.0/utils/parse/yaml/parser.go#L26

Is it safe to concurrently read and write to a viper?
No, you will need to synchronize access to the viper yourself (for example by using the sync package). Concurrent reads and writes can cause a panic.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.