Add git config --global --add safe.directory for vendor/drupal/coder not to let Git 2.35 block the automated update process

[Natshah]

Git security vulnerability announced
https://github.blog/2022-04-12-git-security-vulnerability-announced/
for Git 2.35

Git 2.36

Stricter repository ownership checks
https://github.blog/2022-04-18-highlights-from-git-2-36/#stricter-repository-ownership-checks

Latest source Release
Git 2.37.1 went out too - Release Notes (2022-07-04)

safe.directory
These config entries specify Git-tracked directories that are considered safe even if they are owned by someone other than the current user. By default, Git will refuse to even parse a Git config of a repository owned by someone else, let alone run its hooks, and this config setting allows users to specify exceptions, e.g. for intentionally shared repositories (see the --shared option in git-init[1]).

A system with the latest version of git may face a blocker issue on update
If the maintainer of the project did not yet add the drupal coder to the safe directory list
Listing ~/.gitconfig

[user]
        name = Rajab Natshah
        email = rajabn@gmail.com
[http]
        version = HTTP/2
[safe]
        directory = /var/www/html/products/project_browser
        directory = /var/www/html/products/varbase
        directory = /var/www/html/products/varbase_core
        directory = /var/www/html/products/varbase_api
        directory = /var/www/html/products/vartheme_bs4
        directory = /var/www/html/products/vartheme_bs5
        directory = /var/www/html/products/varbase_layout_builder
        directory = /var/www/html/test/varbase906t1/vendor/drupal/coder