Description

This PR will eliminate a potential recursive definition. It will benefit users who want to use vi mode in zsh.

Motivation and Context

Closes #3418
Closes #5522

Current src/init/starship.zsh has a potential risk to cause recursive definition of starship_zle-keymap-select-wrapped when user set vi mode.

for example:

use this minimal zshrc:

bindkey -v
eval "$(starship init zsh)"

then start a terminal, type source ~/.zshrc twice

~
❯ source ~/.zshrc
~
❯ source ~/.zshrc

press ESC to trigger vi normal mode, error message show bellow:

~ 
❯ 
starship_zle-keymap-select-wrapped:1: maximum nested function level reached; increase FUNCNEST?
~ 
❯ 

check starship_zle-keymap-select-wrapped and __starship_preserved_zle_keymap_select

~
❯ which starship_zle-keymap-select-wrapped
starship_zle-keymap-select-wrapped () {
	$__starship_preserved_zle_keymap_select "$@"
	starship_zle-keymap-select "$@"
}
~
❯ echo $__starship_preserved_zle_keymap_select
starship_zle-keymap-select-wrapped

see a recursive definition

How Has This Been Tested?

• I have tested using MacOS
• I have tested using Linux
• I have tested using Windows

I use this minimal zshrc:

bindkey -v
eval "$(~/github-project/starship/target/debug/starship init zsh)"

~/github-project/starship/target/debug/starship is the binary which I build.

repeat the operations, vi mode works well and no error is reported.

and user defined action works as well:

bindkey -v
function myfoo() {
        echo "\nhello world\n"
}
zle -N zle-keymap-select myfoo; # print "hello world" every time swtich the vi mode
eval "$(~/github-project/starship/target/debug/starship init zsh)"

Checklist:

• I have updated the documentation accordingly.
• I have updated the tests accordingly.