Fix code block language tags for proper syntax highlighting (#8189)

Replace ``` text with appropriate language tags (php, bash, html)
across 34 documentation files to enable proper syntax highlighting.

Blocks that are genuinely plain text (URL patterns, crontab entries,
ICU format syntax, print_r output) are intentionally left as text.

Author: dereuromark

docs/en/appendices/5-0-upgrade-guide.md

@@ -6,7 +6,7 @@ First, check that your application is running on latest CakePHP 4.x version.
 
 Once your application is running on latest CakePHP 4.x, enable deprecation warnings in **config/app.php**:
 
-``` text
+``` php
 'Error' => [
     'errorLevel' => E_ALL,
 ]
@@ -49,7 +49,7 @@ composer install --no-dev
 With the upgrade tool installed you can now run it on your application or
 plugin:
 
-``` text
+``` bash
 bin/cake upgrade rector --rules cakephp50 <path/to/app/src>
 bin/cake upgrade rector --rules chronos3 <path/to/app/src>
 ```

docs/en/appendices/5-1-migration-guide.md

@@ -10,7 +10,7 @@ The [upgrade tool](../appendices/migration-guides) provides rector rules for
 automating some of the migration work. Run rector before updating your
 `composer.json` dependencies:
 
-``` text
+``` bash
 bin/cake upgrade rector --rules cakephp51 <path/to/app/src>
 ```
 

docs/en/appendices/5-2-migration-guide.md

@@ -10,7 +10,7 @@ The [upgrade tool](../appendices/migration-guides) provides rector rules for
 automating some of the migration work. Run rector before updating your
 `composer.json` dependencies:
 
-``` text
+``` bash
 bin/cake upgrade rector --rules cakephp52 <path/to/app/src>
 ```
 

docs/en/appendices/5-3-migration-guide.md

@@ -10,7 +10,7 @@ The [upgrade tool](../appendices/migration-guides) provides rector rules for
 automating some of the migration work. Run rector before updating your
 `composer.json` dependencies:
 
-``` text
+``` bash
 bin/cake upgrade rector --rules cakephp53 <path/to/app/src>
 ```
 

docs/en/appendices/glossary.md

@@ -56,7 +56,7 @@ columns. Often used in conjunction with the FormHelper.
 HTML attributes
 An array of key =\> values that are composed into HTML attributes. For example:
 
-``` text
+``` php
 // Given
 ['class' => 'my-class', 'target' => '_blank']
 
@@ -67,7 +67,7 @@ class="my-class" target="_blank"
 If an option can be minimized or accepts its name as the value, then `true`
 can be used:
 
-``` text
+``` php
 // Given
 ['checked' => true]
 
@@ -87,7 +87,7 @@ plugin syntax
 Plugin syntax refers to the dot separated class name indicating classes
 are part of a plugin:
 
-``` text
+``` php
 // The plugin is "DebugKit", and the class name is "Toolbar".
 'DebugKit.Toolbar'
 

docs/en/appendices/migration-guides.md

@@ -12,7 +12,7 @@ method renames and signature updates.
 
 To use the upgrade tool:
 
-``` text
+``` bash
 # Install the upgrade tool
 git clone https://github.com/cakephp/upgrade
 cd upgrade

docs/en/console-commands/cache.md

@@ -3,7 +3,7 @@
 To help you better manage cached data from a CLI environment, a console command
 is available for clearing cached data your application has:
 
-``` text
+``` bash
 // Clear one cache config
 bin/cake cache clear <configname>
 

docs/en/console-commands/commands.md

@@ -91,7 +91,7 @@ CakePHP will use conventions to generate the name your commands use on the
 command line. If you want to overwrite the generated name implement the
 `defaultName()` method in your command:
 
-``` text
+``` php
 public static function defaultName(): string
 {
     return 'oh_hi';

docs/en/contributing/backwards-compatibility.md

@@ -272,7 +272,7 @@ locate code that needs to be updated before it breaks. If you wish to disable
 runtime warnings you can do so using the `Error.errorLevel` configuration
 value:
 
-``` text
+``` php
 // in config/app.php
 // ...
 'Error' => [

docs/en/contributing/cakephp-coding-conventions.md

@@ -32,7 +32,7 @@ Four spaces will be used for indentation.
 
 So, indentation should look like this:
 
-``` text
+``` php
 // base level
     // level 1
         // level 2
@@ -98,7 +98,7 @@ In short:
 Control structures are for example "`if`", "`for`", "`foreach`",
 "`while`", "`switch`" etc. Below, an example with "`if`":
 
-``` text
+``` php
 if ((expr_1) || (expr_2)) {
     // action_1;
 } elseif (!(expr_3) && (expr_4)) {
@@ -368,7 +368,7 @@ tags:
 PhpDoc tags are very much like JavaDoc tags in Java. Tags are only processed if
 they are the first thing in a DocBlock line, for example:
 
-``` text
+``` php
 /**
  * Tag example.
  *
@@ -377,7 +377,7 @@ they are the first thing in a DocBlock line, for example:
  */
 ```
 
-``` text
+``` php
 /**
  * Example of inline phpDoc tags.
  *
@@ -467,7 +467,7 @@ public function foo()
 `include`, `require`, `include_once` and `require_once` do not have
 parentheses:
 
-``` text
+``` php
 // wrong = parentheses
 require_once('ClassFileName.php');
 require_once ($class);
@@ -491,7 +491,7 @@ The short echo should be used in template files in place of `<?php echo`. It
 should be immediately followed by a single space, the variable or function value
 to `echo`, a single space, and the php closing tag:
 
-``` text
+``` php
 // wrong = semicolon, no spaces
 <td><?=$name;?></td>
 
@@ -593,22 +593,22 @@ of `floatval($var)` when applicable.
 
 Constants should be defined in capital letters:
 
-``` text
+``` php
 define('CONSTANT', 1);
 ```
 
 If a constant name consists of multiple words, they should be separated by an
 underscore character, for example:
 
-``` text
+``` php
 define('LONG_NAMED_CONSTANT', 2);
 ```
 
 ### Enums
 
 Enum cases are defined in `CamelCase` style:
 
-``` text
+``` php
 enum ArticleStatus: string
 {
     case Published = 'Y';