docs(remote): 📝 Add notes for Windows user on sharing git credentials (GPG keys) (#6194)

* docs(remote): 📝 update sharing-git-credentials.md

Adding a note for Windows user.
The GPG signing keys must be defined in the WSL distro as it is the OS shared with the DevContainer.

* docs(remote): 📝 add note for gpg sharing

update notes for Windows users.
Note on sharing gpg keys with devcontainer.

* docs(remote): 📝 update sharing gpg keys

fix notes and comments on how to setup gpg keys in windows.

remote/advancedcontainers/sharing-git-credentials.md

@@ -85,6 +85,10 @@ If you do not have GPG set up, you can configure it for your platform:
   * Register a `pinentry` GUI in your WSL distro. `echo pinentry-program /mnt/c/Program\ Files\ \(x86\)/Gpg4win/bin/pinentry.exe > ~/.gnupg/gpg-agent.conf`
   * Reload the `gpg` agent in WSL. `gpg-connect-agent reloadagent /bye`
 
+> **Note**
+> For Windows user, the gpg signing key must be setup using the Windows GUI or cli (powershell/cmd) and not in the Git Bash.
+> The DevContainer can't access the gpg keys configured in Git Bash even though it is in your `~/.gnupg/` folder, accessible in the Windows explorer.
+
 Next, install `gnupg2` in your container by updating your Dockerfile.
 
 For example:
@@ -99,6 +103,8 @@ Or if running as a [non-root user](/remote/advancedcontainers/add-nonroot-user.m
 RUN sudo apt-get update && sudo apt-get install gnupg2 -y
 ```
 
+To apply your config changes, you need to rebuild the container. You can do this by running **Dev Containers: Rebuild Container** from the Command Palette (`F1`).
 The next time the container starts, your GPG keys should be accessible inside the container as well.
 
-> **Note:** If you used `gpg` previously in the container, you may need to run **Dev Containers: Rebuild Container** for the update to take effect.
+> **Note**
+> If you used `gpg` previously in the container, you may need to run **Dev Containers: Rebuild Container** for the update to take effect.