Deprecated AUTO_ADD_TRY_UMOUNT_FOR_BIND_MOUNT, the leftover add_sus_mount cli and umount_for_zygote_system_process

Reason:
 - AUTO_ADD_TRY_UMOUNT_FOR_BIND_MOUNT is also causing a bit more performance overheads and still it cannot catch all the sus mounts in all situations. Actually it can easily be done in boot-completed.sh, and it should be more accurate, see module templates for more details.

- Official KernelSU also allows ksud to add custom path to try_umount list as well, users can use their own way to add only the desired sus mounts to try_umount list, but remember to disable susfs ADD_TRY_UMOUNT in kernel if users want to use the official one.

- There are less use cases for umount_for_zygote_system_process, and sometimes enabling this may cause bootloop with some modules enabled, instead user can use busybox nsenter to umount the sus mounts for specific process later by themmselves.

Co-authored-by: simonpunk <simonpunk2016@gmail.com>

kernel/Kconfig

@@ -99,16 +99,7 @@ config KSU_SUSFS_TRY_UMOUNT
 	default y
 	help
 		- Allow using try_umount to umount other user-defined mount paths prior to ksu's default umount paths.
-		- Effective on all NO-root-access-granted processes.
-
-config KSU_SUSFS_AUTO_ADD_TRY_UMOUNT_FOR_BIND_MOUNT
-	bool "Enable to add bind mounts to ksu's try_umount automatically (experimental)"
-	depends on KSU_SUSFS_TRY_UMOUNT
-	default y
-	help
-		- Automatically add binded mounts to ksu's try_umount.
-		- No susfs command is needed in userspace.
-		- Only mount operation from process with ksu domain will be checked.
+		- Effective only on zygote spawned umounted user app process.
 
 config KSU_SUSFS_SPOOF_UNAME
 	bool "Enable to spoof uname"