use user-defined allocator to configure logging.

[fujitatomoya]

address #1036

[iuhilnehc-ynos]

on rcl layer, there are two exported functions to set allocator for rcutils log module.

1. rcl_logging_configure -> rcl_logging_configure_with_output_handler
2. rcl_logging_configure_with_output_handler

If a component(such as rclcpp) doesn't call the above functions, logging functions on rcutils layer use the default allocator by the RCUTILS_LOGGING_AUTOINIT.

I think it makes sense.

[iuhilnehc-ynos]

and we need to remove

rcl/rcl/src/rcl/init.c

Lines 71 to 74 in cae279a

	RCUTILS_LOG_DEBUG_NAMED(
	ROS_PACKAGE_NAME,
	"Initializing ROS client library, for context at address: %p", (void *) context);

.

[fujitatomoya]

and we need to remove

rcl/rcl/src/rcl/init.c

Lines 71 to 74 in cae279a

	RCUTILS_LOG_DEBUG_NAMED(
	ROS_PACKAGE_NAME,
	"Initializing ROS client library, for context at address: %p", (void *) context);

.

this one has been already pointed out by #1037, i believe that each PR should be against specific issue. So i will not address it here.

[fujitatomoya]

CI:

• Linux
• Linux-aarch64
• Windows

[fujitatomoya]

CI:

• Linux
• Linux-aarch64
• Windows

[fujitatomoya]

https://ci.ros2.org/job/ci_windows/18945/#showFailuresLink unstable failure is not related to this PR.