Unnecessary environmental variables for Fcitx5 are set

[possior]

In bash.sh, GTK_IM_MODULE and QT_IM_MODULE environmental variables are set to "fcitx. They are not recommended by Using Fcitx5 on Wayland documentation as below. These two environmental variables should be removed from bash.sh, though Fcitx5 can run even with them set.

KDE Plasma

Best setup:

    KDE Plasma 5.27 or later
    Environment variables:
        Set XMODIFIERS=@im=fcitx for XWayland application
        Start fcitx5 by go to "System settings" -> "Virtual keyboard" -> Select Fcitx 5
        Do not set GTK_IM_MODULE & QT_IM_MODULE & SDL_IM_MODULE . You could unset GTK_IM_MODULE & QT_IM_MODULE by runing im-config and then selecting do not set any IM from im-config and use desktop default"
        Run chromium/electron application with --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime
    Caveats:
        Certain Gtk/Qt application that only works under X11 may still need to set GTK_IM_MODULE or QT_IM_MODULE for them individually.
        If you set GTK_IM_MODULE/QT_IM_MODULE globally, you will hit this issue [Candidate window is blinking under wayland with Fcitx 5](https://fcitx-im.org/wiki/Special:MyLanguage/FAQ#Candidate_window_is_blinking_under_wayland_with_Fcitx_5)

Support Information:

    App/Compositor supports text-input-v2 and text-input-v3.
    Comopositor/Application uses zwp_input_method_v1.
    5.27 additionally supports text-input-v1.
    5.24 usable zwp_input_method_v1 with fcitx5. Pre-5.24 there are lots of problems, always use fcitx im module instead.
    Use "Virtual keyboard" KCM to launch fcitx5. This is required to use text-input protocol. If you launch fcitx this way, make sure you do not use "restart" in the tray menu, since the socket passed from KWin can not be reused with the newly restarted fcitx.