[CBRD-25359] uhosts version of freeaddrinfo () to release memory explicitly

[kisoo-han]

http://jira.cubrid.org/browse/CBRD-25359

Description

• because uhosts alloc memory using malloc () and free using freeaddrinfo (), CUBRID memory utility cannot catch memory release point inside freeaddrinfo (3) glibc library.
• we will introduce new function, freeaddrinfo_uhost (), and in case uhosts enabled, we will free memory allocated by getaddrinfo () externally using free (3).

[hornetmj]

It is good to me to replace malloc to MALLOC() macro if you want to use FREE_MEM() macro. Or how about use free()?

[kisoo-han]

I think it's a good idea to use MALLOC and FREE_MEM as a pair in point of memory managements.
fixed.

[Rudeus]

Since this issue occurs in a situation where memory monitoring project is applied, I believe it is appropriate to change the target branch for merging from the develop branch to the feature/memory_monitoring_ver2_merge branch.

[hornetmj]

Since this issue occurs in a situation where memory monitoring project is applied, I believe it is appropriate to change the target branch for merging from the develop branch to the feature/memory_monitoring_ver2_merge branch.

@kisoo-han To explain further, we are performing regression testing in {{memory_monitoring_ver2_merge}} branch. We requested this because we thought it would be better if the changes made in this PR were verified together. I feel like the request was made without sufficient reason, so I would like to explain further. thank you for the quick response. Also, I apologize for the sudden change request.

[kisoo-han]

This issue will be moved to #5211 due to base branch problem.