move probe to values and restore default values

https://github.com/deepflowys/deepflow/issues/544 issues 暴露了我们一些地方排查的不方便，我们会进行一些改动

将探活从tcp改为http，同时代码层面做如下改动 : server启动后20417 端口可工作，但是直到阻塞式的各项操作完成后才让 20417 回复200，未完成时打印日志：我还没启动，因为什么原因没启动，并回复503.(TBD)
探活的策略放到values中，用户可根据自己的环境进行自定义修改
恢复探活的时间为默认，我们认为之前默认时间是个大部分情况下的预期的合理时间，这样能发现潜在问题。
我们会遇到很多环境，很多问题，以后也不能总用增大这个时间来解决，我们需要将这些配置放到values中，让用户可自定义。
我们会在数据库开始执行init时候记录log，执行完成记录log，以便后续更方便的定位到这个问题。(TBD)

https://github.com/deepflowys/deepflow/issues/544 issues expose the inconvenience of our investigation in some places, we will make some changes

Change the probe from tcp to http, and make the following changes at the code level: After the server starts, the 20417 port can work, but 20417 will not reply 200 until the blocking operations are completed, and print the log when it is not completed: I It hasn't started yet, because it didn't start for some reason, and replied 503. (TBD)
The active strategy is placed in the values, and users can customize and modify them according to their own environment
The time to resume exploration is the default. We believe that the previous default time is a reasonable time expected in most cases, so that potential problems can be found.
We will encounter many environments and many problems, which cannot always be solved by increasing this time in the future. We need to put these configurations into values so that users can customize them.
We will record the log when the database starts to execute init, and record the log when the execution is completed, so that the problem can be more easily located in the future. (TBD)

deepflowio / deepflow-charts