scripts/lint: avoid unexpected vimlint failure

After a GitHub runner release of the ubuntu:22.04 in February, the
vimlint call started failing. This seems to be for two reasons that work
in concert. First, vimlint was exiting non-zero and causing script/lint
to exit without reporting vimlint's output, because scripts/lint had
errexit set, causing it exit immediately. Second, the call depth being
analysed by vimlint exceeded maxfuncdepth, so set it to a higher value
by leveraging VIMLINT_VIM to set maxfuncdepth to 200 to avoid vimlint
exiting non-zero due to that.

Author: bhcleek

scripts/lint

@@ -48,6 +48,7 @@ fi
 ### Run vim-vimlint
 ###################
 printf "Running vim-vimlint ... \n" >&2
+set +e
 lint=$(sh "$vimdir/share/vim/vimgo/pack/vim-go/start/vim-vimlint/bin/vimlint.sh" \
   -p "$vimdir/share/vim/vimgo/pack/vim-go/start/vim-vimlparser" \
   -l "$vimdir/share/vim/vimgo/pack/vim-go/start/vim-vimlint" \
@@ -57,6 +58,7 @@ lint=$(sh "$vimdir/share/vim/vimgo/pack/vim-go/start/vim-vimlint/bin/vimlint.sh"
   "$vimgodir" \
   2>&1)
 result="$?"
+set -e
 if [ "$result" -eq "2" ]; then
   printf "FAILED\n" >&2
   printf "$lint" >&2