Rename LIB_ to LIBC_ for all libc Kconfig

follow other libc component naming convention

Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>

Documentation/applications/nsh/commands.rst

@@ -193,7 +193,7 @@ Also sets the previous working directory environment variable
 ``cd -``            sets the current working directory to the previous
                     working directory ($OLDPWD). Equivalent to cd $OLDPWD.
 ``cd`` or ``cd ~``  set the current working directory to the 'home' directory.
-                    The home directory can be configured by setting CONFIG_LIB_HOMEDIR
+                    The home directory can be configured by setting CONFIG_LIBC_HOMEDIR
                     in the configuration file. The default home directory is /.
 ``cd ..`` 	        sets the current working directory to the parent directory.
 ==================  =====================================

Documentation/components/binfmt.rst

@@ -180,7 +180,7 @@ Basic module management
     The ``filename`` field will be used
     in order to locate the module to be loaded from the file system.
     The filename must be the full, absolute path to the file to be executed
-    unless ``CONFIG_LIB_ENVPATH`` is defined. In that case, filename may be
+    unless ``CONFIG_LIBC_ENVPATH`` is defined. In that case, filename may be
     a relative path; a set of candidate absolute paths will be generated using
     the ``PATH`` environment variable and ``load_module()`` will attempt to load each
     file that is found at those absolute paths.

Documentation/reference/os/wqueue.rst

@@ -159,11 +159,11 @@ depend on internal, kernel-space facilities.
 
 **Configuration Options**.
 
--  ``CONFIG_LIB_USRWORK``. If CONFIG_LIB_USRWORK is also defined
+-  ``CONFIG_LIBC_USRWORK``. If CONFIG_LIBC_USRWORK is also defined
    then the user-mode work queue will be enabled.
--  ``CONFIG_LIB_USRWORKPRIORITY``. The execution priority of the
+-  ``CONFIG_LIBC_USRWORKPRIORITY``. The execution priority of the
    user-mode priority worker thread. Default: 100
--  ``CONFIG_LIB_USRWORKSTACKSIZE``. The stack size allocated for
+-  ``CONFIG_LIBC_USRWORKSTACKSIZE``. The stack size allocated for
    the lower priority worker thread. Default: 2048.
 
 

Documentation/reference/user/01_task_control.rst

@@ -405,7 +405,7 @@ Functions
   exits.
 
   :param filename: The path to the program to be executed. If
-     ``CONFIG_LIB_ENVPATH`` is defined in the configuration, then this may
+     ``CONFIG_LIBC_ENVPATH`` is defined in the configuration, then this may
      be a relative path from the current working directory. Otherwise,
      ``path`` must be the absolute path to the program.
   :param argv: A pointer to an array of string arguments. The end of the
@@ -469,7 +469,7 @@ Functions
   task.
 
   :param path: The path to the program to be executed. If
-     ``CONFIG_LIB_ENVPATH`` is defined in the configuration, then this may
+     ``CONFIG_LIBC_ENVPATH`` is defined in the configuration, then this may
      be a relative path from the current working directory. Otherwise,
   :param path: must be the absolute path to the program.
 
@@ -489,7 +489,7 @@ Functions
   information.
 
   :param path: The path to the program to be executed. If
-     ``CONFIG_LIB_ENVPATH`` is defined in the configuration, then this may
+     ``CONFIG_LIBC_ENVPATH`` is defined in the configuration, then this may
      be a relative path from the current working directory. Otherwise,
   :param path: must be the absolute path to the program.
 
@@ -530,7 +530,7 @@ Functions
     variable PATH.
 
     NOTE: NuttX provides only one implementation: If
-    ``CONFIG_LIB_ENVPATH`` is defined, then only ``posix_spawnp()``
+    ``CONFIG_LIBC_ENVPATH`` is defined, then only ``posix_spawnp()``
     behavior is supported; otherwise, only ``posix_spawn`` behavior is
     supported.
 
@@ -584,8 +584,8 @@ Functions
   **Assumptions/Limitations:**
 
   -  NuttX provides only ``posix_spawn()`` or ``posix_spawnp()`` behavior
-     depending upon the setting of ``CONFIG_LIB_ENVPATH``: If
-     ``CONFIG_LIB_ENVPATH`` is defined, then only ``posix_spawnp()``
+     depending upon the setting of ``CONFIG_LIBC_ENVPATH``: If
+     ``CONFIG_LIBC_ENVPATH`` is defined, then only ``posix_spawnp()``
      behavior is supported; otherwise, only ``posix_spawn()`` behavior is
      supported.
   -  The ``envp`` argument is not used and the ``environ`` variable is not