Incompatibility with custom config setopt shwordsplit

Hi,

Here is an issue noticed during my move to zimfw (from a basic zsh, without any framework), when importing my existing zsh customizations.

[x] I've checked the existing issues and I'm not duplicating a report.
[x] I'm using the latest version of zimfw.
[x] I've checked the Changelog and I'm not being affected by documented changes.
[x] I've checked the 📢 Announcements and I'm not being affected by announced changes.
[x] I was able to reproduce the issue with a clean installation of Zim.
[x] I've pasted the output of zimfw info below.

Describe the bug
git-info doesn't work in a git directory, when using "setopt shwordsplit" (typically used in my .zshrc)

Steps to reproduce

Go in a git directory

~
% cd .zim/modules/utility

~/.zim/modules/utility on master
%

set option shwordsplit

~/.zim/modules/utility on master
% setopt shwordsplit
git-info:zformat:232: invalid argument: %%B%F{magenta}%b%c%s${(e)git_info[status]:+"

~/.zim/modules/utility
%

=> error

unset option shwordsplit


~/.zim/modules/utility
% unsetopt shwordsplit

~/.zim/modules/utility on master %

=> no issue anymore

**Current behavior**  
In step 2. we notice the error :
_git-info:zformat:232: invalid argument: %%B%F{magenta}%b%c%s${(e)git_info[status]:+"_

**Expected behavior**  
Ideally, user configurations should not affect the behavior of Zim.

**zimfw info**

% zimfw info zimfw version: 1.10.0 (built at 2022-09-27 22:44:10 UTC, previous commit is 05b8e0c) OSTYPE: linux-gnu TERM: xterm-256color TERM_PROGRAM: TERM_PROGRAM_VERSION: ZIM_HOME: /tmp/tmp.FjTXshbGLs/.zim ZSH_VERSION: 5.8.1


**Additional context**  
Maybe this plugin (and also others) should use something like "emulate -L zsh" ?

According to man zshoptions :

   LOCAL_OPTIONS <K>
          If this option is set at the point of return from a shell  func‐
          tion, most options (including this one) which were in force upon
          entry to the function are restored; options  that  are  not  re‐
          stored  are PRIVILEGED and RESTRICTED.  Otherwise, only this op‐
          tion, and the LOCAL_LOOPS, XTRACE and  PRINT_EXIT_VALUE  options
          are  restored.   Hence  if  this  is explicitly unset by a shell
          function the other options in force at the point of return  will
          remain  so.   A shell function can also guarantee itself a known
          shell configuration with a formulation like  `emulate  -L  zsh';
          the -L activates LOCAL_OPTIONS.



Unless there is a way to do this in zimfw/zimfw rather than in each module.

Thanks

zimfw / git-info

Incompatibility with custom config setopt shwordsplit #3