dyups: fixed bug of deleting wrong upstream check dynamic peers

[shuiuii]

…le IP addresses, call them

如果upstrem下的server是域名的情况下，并且这个域名解析出来对应的多个ip地址，这里需要分别调用多次
因为添加的时候对多个ip分别进行了添加，启动定时器去做健康检查功能，所以删除的时候也需要同步删除。不然会存在定时器泄露，而定时器里面访问相关变量时会奔溃

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

zhusy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[chobits]

Nice catch,

For source detail, add peer occurs in:

tengine/src/http/ngx_http_upstream_round_robin.c

Lines 116 to 123 in 67c72d5

	#if (NGX_HTTP_UPSTREAM_CHECK)
	if (!server[i].down) {
	peer[n].check_index =
	ngx_http_upstream_check_add_peer(cf, us,
	&server[i].addrs[j]);
	} else {
	peer[n].check_index = (ngx_uint_t) NGX_ERROR;
	}

[chobits]

After this #1660 merged, all related test case passed. (dyups.t)