Remove logic for explicitly setting INCLUDE_DIRECTORIES from INTERFACE_INCLUDE_DIRECTORIES of LINK_LIBRARIES passed to libmexclass_client_add_proxy_library

[kevingurney]

In libmexclass_client_add_proxy_library, the LINK_LIBRARIES argument allows clients to specify additional libraries to link against.

Currently, libmexclass_client_add_proxy_library has custom logic for manually adding the INTERFACE_INCLUDE_DIRECTORIES of all LINK_LIBRARIES to the INCLUDE_DIRECTORIES property of the client Proxy library target.

However, CMake does this automatically by default when target_link_libraries is called (i.e. CMake propagates the "usage requirements" of dependencies). Therefore, this custom logic can be removed.

Included below is a relevant excerpt from the CMake documentation for "Transitive Usage Requirements":

Usage requirements are propagated by reading the INTERFACE_ variants of target properties from dependencies and appending the values to the non-INTERFACE_ variants of the operand. For example, the INTERFACE_INCLUDE_DIRECTORIES of dependencies is read and appended to the INCLUDE_DIRECTORIES of the operand.

[kevingurney]

Please refer to this discussion on apache/arrow#34563 for more information.