Update preset regex and simplify Readme test

Removed the unnecessary YML content manipulation from the Readme test in ReadmeTest.php. Furthermore, updated the regex pattern for alias in presets in the README.md file to case insensitive, easing the matching process. Improved the readability of the description for the preset_database.yml.

README.md

@@ -938,7 +938,8 @@ In fact, this can be considered as partial inheritance.
  - Schemas with presets validate themselves and if there are any obvious issues, you will see them when you try to use
   the schema.
  - Alias in presets must match the regex pattern
-   <!-- auto-update:preset-regex -->`/^[a-z0-9-_]+$/i`<!-- auto-update:/preset-regex -->.
+   <!-- auto-update:preset-regex --> `"/^[a-z0-9-_]+$/i"` <!-- auto-update:/preset-regex -->.
+   Otherwise, it might break the syntax.
 
 
 Let's take a look at what this looks like in code.

tests/ReadmeTest.php

@@ -196,7 +196,7 @@ public function testCheckPresetFeaturesExampleInReadme(): void
     public function testCheckPresetRegexInReadme(): void
     {
         $text = SchemaDataPrep::getAliasRegex();
-        Tools::insertInReadme('preset-regex', "`{$text}`", true);
+        Tools::insertInReadme('preset-regex', " `\"{$text}\"` ", true);
     }
 
     public function testCheckPresetDatabaseExampleInReadme(): void

tests/Tools.php

@@ -118,7 +118,7 @@ public static function insertInReadme(string $code, string $content, bool $isInl
         if ($isInline) {
             $replacement = \implode('', [
                 "<!-- {$prefix}{$code} -->",
-                \trim($content),
+                $content,
                 "<!-- {$prefix}/{$code} -->",
             ]);
         } else {