doc: normalize shell code block info strings

Prior to this commit, shell fenced code blocks in Markdown files had
inconsistent info strings. This has been corrected to standarize on
the one with the highest frequency in the doc/api/ dir.

Stats:
> 'console' => 54,
> 'shell' => 2,

PR-URL: #33486
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>

Author: Derek Lewis

README.md

@@ -572,7 +572,7 @@ Primary GPG keys for Node.js Releasers (some Releasers sign with subkeys):
 
 To import the full set of trusted release keys:
 
-```shell
+```bash
 gpg --keyserver pool.sks-keyservers.net --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C
 gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
 gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1

doc/api/intl.md

@@ -119,13 +119,13 @@ through either:
 
 * The [`NODE_ICU_DATA`][] environment variable:
 
-  ```shell
+  ```bash
   env NODE_ICU_DATA=/some/directory node
   ```
 
 * The [`--icu-data-dir`][] CLI parameter:
 
-  ```shell
+  ```bash
   node --icu-data-dir=/some/directory
   ```
 

doc/guides/backporting-to-release-lines.md

@@ -35,7 +35,7 @@ replace that with the staging branch for the targeted release line.
 2. Make sure that the local staging branch is up to date with the remote.
 3. Create a new branch off of the staging branch, as shown below.
 
-    ```shell
+    ```bash
     # Assuming your fork of Node.js is checked out in $NODE_DIR,
     # the origin remote points to your fork, and the upstream remote points
     # to git://github.com/nodejs/node
@@ -55,7 +55,7 @@ replace that with the staging branch for the targeted release line.
    will likely fail due to conflicts. In that case, you will see something
    like this:
 
-    ```shell
+    ```console
     # Say the $SHA is 773cdc31ef
     $ git cherry-pick $SHA # Use your commit hash
     error: could not apply 773cdc3... <commit title>

doc/guides/maintaining-V8.md

@@ -324,7 +324,7 @@ that Node.js may be floating (or else cause a merge conflict).
 
 The rough outline of the process is:
 
-```shell
+```bash
 # Assuming your fork of Node.js is checked out in $NODE_DIR
 # and you want to update the Node.js master branch.
 # Find the current (OLD) version in
@@ -363,15 +363,15 @@ above. A better strategy is to
 
 To audit for floating patches:
 
-```shell
+```bash
 git log --oneline deps/v8
 ```
 
 To replace the copy of V8 in Node.js, use the [`git-node`][] tool. For example,
 if you want to replace the copy of V8 in Node.js with the branch-head for V8 5.1
 branch:
 
-```shell
+```bash
 cd $NODE_DIR
 git node v8 major --branch=5.1-lkgr
 ```

doc/guides/maintaining-root-certs.md

@@ -30,7 +30,7 @@ the nodejs/node repository.
 
     Update the tag in the commands below, and run:
 
-    ```shell
+    ```bash
     cd tools/
     ./mk-ca-bundle.pl -v 2>_before
     curl -O https://hg.mozilla.org/projects/nss/raw-file/NSS_3_41_RTM/lib/ckfw/builtins/certdata.txt
@@ -57,15 +57,15 @@ the nodejs/node repository.
 
     Run the command below:
 
-    ```shell
+    ```bash
     ./mk-ca-bundle.pl -v 2>_after
     ```
 
     Confirm that `../src/node_root_certs.h` was updated.
 
     Determine what changes were made by diffing the before and after files:
 
-    ```shell
+    ```console
     % diff _before _after
     11d10
     < Parsing: Visa eCommerce Root

doc/guides/maintaining-zlib.md

@@ -6,7 +6,7 @@ performance improvements not currently available in standard zlib.
 ## Updating zlib
 
 Update zlib:
-```shell
+```bash
 git clone https://chromium.googlesource.com/chromium/src/third_party/zlib
 cp deps/zlib/zlib.gyp deps/zlib/win32/zlib.def deps
 rm -rf deps/zlib zlib/.git