Update rules for code fence syntax highlighting language name conversion

Author: echeran

src/content/docs/1_5/tutorials/cargo.md

@@ -24,7 +24,7 @@ In your main.rs, you can use all stable ICU4X components for the recommended set
 If you wish to use custom compiled data for ICU4X, no changes to Cargo.toml are required. Instead, set the `ICU4X_DATA_DIR` environment variable to the
 datagen output during your build:
 
-```command
+```shell
 icu4x-datagen --format mod --keys all --locales ru --out baked_data
 ICU4X_DATA_DIR=$(pwd)/baked_data cargo build --release
 ```

src/content/docs/1_5/tutorials/data-management.md

@@ -54,7 +54,7 @@ If you check in the generated data, it is recommended that you configure a job i
 
 Once we have generated the data, we need to instruct `ICU4X` to use it. To do this, set the `ICU4X_DATA_DIR` during the compilation of your app:
 
-```command
+```shell
 ICU4X_DATA_DIR=$(pwd)/my_data cargo run
 ```
 

tools/github-to-astro.ts

@@ -53,6 +53,7 @@ function icu4xAstroMdFrontMatter(foundTitle: string) {
 const ICU4X_MD_REPLACEMENTS: Array<{pattern: string | RegExp; replacement: string}> = [
   // fix the code fence syntax highlighting language identifers
   {pattern: /```console.*/g, replacement: "```shell"},
+  {pattern: /```command.*/g, replacement: "```shell"},
   {pattern: /```rust.*/g, replacement: "```rust"},
 
   // remove H1 titles from MD pages in Github (because Front Matter is the way to