next-susfs-4.9

patch buat nambahin susfs di KernelSU-Next

• kernel: Remove support for Shamiko
• Making mountinfo visible to ksu process somehow would leak traces on some devices
• We should not make things compatible with any closed source softwares as their code can be updated at anytime and we do not know what to adapt to the changes
• latest Shamiko may not rely on mountinfo anymore so user should still be able to use Shamiko with susfs
• Making mountinfo invisible to all process makes susfs less debuggable again
• KernelSU: Fix compiler not being happy when ENABLE_LOG is disabled
• Bump version to 1.5.5
• KernelSU: forgot to rename try_umount to ksu_try_umount in the last commit
• kernel & KernelSU: TRY_UMOUNT: log try_umount for default ksu mounts as well
• kernel & KernelSU: Rebase susfs patches on KernelSU-v1.0.3
• kernel: SUS_PATH: remove redundant inode_permission check
• kernel: SUS_MOUNT: fix normal mounts that are carelessly hidden in mountinfo
• Bump version to 1.5.4
• KernelSU: Update Kconfig description
• kernel & KernelSU: Enhancement of SUS_MOUNT, fix more possible detections like inherited fdinfo and mnt_id counts; Remove hooks for inode update time functions; Update README.md for patching instruction and ksu_module_susfs
• KernelSU: Fix SET_CMDLINE_OR_BOOTCONFIG feature not working because some defs and functions were not renamed thoroughly
• Forgot to update the CMD name in core_hook.c during this commit https://gitlab.com/simonpunk/susfs4ksu/-/commit/17a73b1a62a8eef0a7a601c57a8b6d98b1c3593f, should be CMD_SUSFS_SET_CMDLINE_OR_BOOTCONFIG instead of CMD_SUSFS_SET_PROC_CMDLINE