Add language annotations to codeblocks in resource type descriptions (#267)

## Summary

Codeblocks embedded in the `description` property of many resource types
lacked a language annotation, causing them to render without syntax
highlighting on docs.radapp.io. This adds ` ```bicep ` annotations to
all affected descriptions and documents the requirement in the
contribution guide.

## Reason for change

Unannotated fences (e.g. in `Radius.Compute/containers`) render
incorrectly on docs.radapp.io, unlike the already-correct
`Radius.Compute/containerImages`. Auditing all resource types found 33
unannotated opening fences across 15 files — all Bicep examples.

## How to test

- Verify each modified `*.yaml` still parses and the description renders
with highlighted Bicep in the Radius Dashboard / docs.
- Confirm no opening code fence in any `description` remains without a
language annotation.

## File change summary

| File | Summary of change |
| ---- | ----------------- |
| `Compute/containers/containers.yaml` | Annotate 3 description
codeblocks as `bicep` |
| `Compute/persistentVolumes/persistentVolumes.yaml` | Annotate 4
description codeblocks as `bicep` |
| `Compute/routes/routes.yaml` | Annotate 3 description codeblocks as
`bicep` |
| `Data/redisCaches/redisCaches.yaml` | Annotate 2 description
codeblocks as `bicep` |
| `Data/postgreSqlDatabases/postgreSqlDatabases.yaml` | Annotate 2
description codeblocks as `bicep` |
| `Data/mongoDatabases/mongoDatabases.yaml` | Annotate 2 description
codeblocks as `bicep` |
| `Data/neo4jDatabases/neo4jDatabases.yaml` | Annotate 3 description
codeblocks as `bicep` |
| `Data/sqlServerDatabases/sqlServerDatabases.yaml` | Annotate 2
description codeblocks as `bicep` |
| `Data/mySqlDatabases/mySqlDatabases.yaml` | Annotate 2 description
codeblocks as `bicep` |
| `Messaging/kafka/kafka.yaml` | Annotate 2 description codeblocks as
`bicep` |
| `Messaging/rabbitMQ/rabbitMQ.yaml` | Annotate 1 description codeblock
as `bicep` |
| `AI/search/search.yaml` | Annotate 2 description codeblocks as `bicep`
|
| `AI/models/models.yaml` | Annotate 2 description codeblocks as `bicep`
|
| `Storage/objectStorage/objectStorage.yaml` | Annotate 2 description
codeblocks as `bicep` |
| `Security/secrets/secrets.yaml` | Annotate 1 description codeblock as
`bicep` |
| `docs/contributing/contributing-resource-types-recipes.md` | Require
language annotations on all description codeblocks; convert the
`redisCaches` example from indented to fenced `bicep` blocks |

<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes #266

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Reshma Abdul Rahim <61033581+Reshrahim@users.noreply.github.com>

Author: Copilot

AI/models/models.yaml

@@ -6,7 +6,7 @@ types:
       To deploy a model, add a models resource to the application definition Bicep
       file. The platform-engineer recipe binds this developer-facing contract to a
       managed cloud model service without exposing any module details to the app.
-      ```
+      ```bicep
       resource model 'Radius.AI/models@2025-08-01-preview' = {
         name: 'model'
         properties: {
@@ -19,7 +19,7 @@ types:
 
       To connect your container to the model, create a connection from the
       Container resource to the model as shown below.
-      ```
+      ```bicep
       resource frontend 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'frontend'
         properties: {

AI/search/search.yaml

@@ -10,7 +10,7 @@ types:
       deploy a search service, add a search resource to the application
       definition Bicep file. The platform-engineer recipe provisions the concrete
       backend and maps its endpoint and API key outputs back onto this resource.
-      ```
+      ```bicep
       resource search 'Radius.AI/search@2025-08-01-preview' = {
         name: 'search'
         properties: {
@@ -22,7 +22,7 @@ types:
 
       To connect your container to the service, create a connection from the
       Container resource to the search service as shown below.
-      ```
+      ```bicep
       resource frontend 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'frontend'
         properties: {

Compute/containers/containers.yaml

@@ -4,7 +4,7 @@ types:
     description: |
       The Radius.Compute/containers Resource Type is the primary resource type for running one or more containers. It is always part of a Radius Application. To deploy a Container add a resource to the application definition Bicep file.
 
-      ```
+      ```bicep
       extension radius
       param environment string 
 
@@ -28,7 +28,7 @@ types:
 
       To accept network connections, expose a port on the container.
 
-      ```
+      ```bicep
       resource myContainer 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'myContainer'
         properties: {
@@ -52,7 +52,7 @@ types:
       
       To create an ephemeral emptyDir shared between two containers add a Containers.properties.volumes.
 
-      ```
+      ```bicep
       resource myContainer 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'myContainer'
         properties: {

Compute/persistentVolumes/persistentVolumes.yaml

@@ -4,7 +4,7 @@ types:
     description: |
       The Radius.Compute/persistentVolumes Resource Type represents a persistent storage volume. A PersistentVolume can be referenced in the volumes property of a Container. 
       To deploy, first add a PersistentVolume resource to the application definition Bicep file.
-      ```
+      ```bicep
       extension radius
       param environment string 
 
@@ -21,7 +21,7 @@ types:
       ```
 
       Then reference the PersistentVolume by ID in the volumes property of the Container. Finally, set the mountPath in the container referencing the volumeName.
-      ```
+      ```bicep
       resource myContainer 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'myContainer'
         properties: {
@@ -50,14 +50,14 @@ types:
       ```
 
       PersistentVolumes may be shared across multiple Containers. To mount an existing PersistentVolume in read-only mode, reference the PersistentVolume by name using the `existing` Bicep keyword. For example:
-      ```
+      ```bicep
       resource existingPersistentVolume 'Radius.Compute/persistentVolumes@2025-08-01-preview' existing = {
         name: 'existingPersistentVolume'
       }
       ```
 
       Then add the existing PersistentVolume to the volumes property of a Container with accessMode set to `ReadOnlyMany`.
-      ```
+      ```bicep
       resource myContainer 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'myContainer'
         properties: {

Compute/routes/routes.yaml

@@ -3,7 +3,7 @@ types:
   routes:
     description: |
       The Radius.Compute/routes Resource Type defines network routes for responding to external clients. Note that a Routes resource is not required for service-to-service communication. To use Routes, define a Container and ensure a `containerPort` is specified.
-      ```
+      ```bicep
       extension radius
       param environment string
 
@@ -37,7 +37,7 @@ types:
       ```
 
       Then define a Routes resource.
-      ```
+      ```bicep
       resource ingressRule 'Radius.Compute/routes@2025-08-01-preview' = {
         name: 'ingressRule'
         properties: {
@@ -65,7 +65,7 @@ types:
       The hostname is determined by the Recipe. 
 
       Multiple rules can be included in Routes.
-      ```
+      ```bicep
       resource ingressRule 'Radius.Compute/routes@2025-08-01-preview' = {
         name: 'ingressRule'
         properties: {

Data/mongoDatabases/mongoDatabases.yaml

@@ -7,7 +7,7 @@ types:
       application definition Bicep file. The Azure recipe uses Cosmos DB for
       MongoDB and exposes its endpoint and connection string as resource
       properties.
-      ```
+      ```bicep
       resource database 'Radius.Data/mongoDatabases@2025-08-01-preview' = {
         name: 'mongo'
         properties: {
@@ -20,7 +20,7 @@ types:
 
       To connect your container to the database, create a connection from the
       Container resource to the database as shown below.
-      ```
+      ```bicep
       resource frontend 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'frontend'
         properties: {

Data/mySqlDatabases/mySqlDatabases.yaml

@@ -3,7 +3,7 @@ types:
   mySqlDatabases:
     description: |
       The Radius.Data/mySqlDatabases Resource Type deploys a MySQL database. Provide the administrator `username` and `password` directly on the resource. The `password` property is marked `x-radius-sensitive`, so Radius encrypts it at rest, redacts it on reads, and exposes it (decrypted) only to the platform-engineer recipe that provisions the database.
-      ```
+      ```bicep
       resource mysql 'Radius.Data/mySqlDatabases@2025-08-01-preview' = {
         name: 'mysql'
         properties: {
@@ -21,7 +21,7 @@ types:
       When deploying the application definition, provide the database password value as a parameter. It is recommended to use a password generator such as `openssl` or equivalent. For example, `rad deploy app.bicep -p ****** rand -hex 16)`.
 
       To connect your container to the database, create a connection from the Container resource to the database as shown below.
-      ```
+      ```bicep
       resource myApplication 'Radius.Core/Applications@2025-08-01-preview' = { ... }
 
       resource frontend 'Radius.Compute/containers@2025-08-01-preview' = {

Data/neo4jDatabases/neo4jDatabases.yaml

@@ -5,14 +5,14 @@ types:
       The Radius.Data/neo4jDatabases Resource Type deploys a Neo4j graph database. To create a new Neo4j database, 
       define an Application and Container resource in your application definition Bicep file.
 
-      ```
+      ```bicep
       extension radius
       param environment string
       resource myApplication 'Radius.Core/applications@2025-08-01-preview' = { ... }
       resource myContainer 'Radius.Compute/containers@2025-08-01-preview' = { ... }
       ```
       Then add a `neo4jDatabases` resource.
-      ```
+      ```bicep
       resource neo4j 'Radius.Data/neo4jDatabases@2025-09-11-preview' = {
           name: 'neo4j'
           properties: {
@@ -43,7 +43,7 @@ types:
       When deploying the application definition, provide the database password value as a parameter. It is recommended to use a password generator such as `openssl` or equivalent. For example, `rad deploy app.bicep -p password=$(openssl rand -hex 16)`.
 
       To connect to the new Neo4j database, add a connection between the container and the new Neo4j database. The final Container resource should look similar to:
-      ```
+      ```bicep
       resource myContainer 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'myContainer'
         properties: {

Data/postgreSqlDatabases/postgreSqlDatabases.yaml

@@ -3,7 +3,7 @@ types:
   postgreSqlDatabases:  
     description: |
       The Radius.Data/postgreSqlDatabases Resource Type deploys a PostgreSQL database. Provide the administrator `username` and `password` directly on the resource. The `password` property is marked `x-radius-sensitive`, so Radius encrypts it at rest, redacts it on reads, and exposes it (decrypted) only to the recipe that provisions the database.
-      ```
+      ```bicep
       resource postgresql 'Radius.Data/postgreSqlDatabases@2025-08-01-preview' = {
           name: 'postgresql'
           properties: {
@@ -21,7 +21,7 @@ types:
       When deploying the application definition, provide the database password value as a parameter. It is recommended to use a password generator such as `openssl` or equivalent. For example, `rad deploy app.bicep -p password=$(openssl rand -hex 16)`.
 
       To connect your container to the database, create a connection from the Container resource to the database as shown below. 
-      ```
+      ```bicep
       resource myApplication 'Radius.Core/Applications@2025-08-01-preview' = { ... }
 
       resource frontend 'Radius.Compute/containers@2025-08-01-preview' = {

Data/redisCaches/redisCaches.yaml

@@ -7,7 +7,7 @@ types:
       file. Unlike database types, no secret is required: Azure Managed Redis
       generates its own access keys, so the platform-engineer recipe needs no
       injected credentials.
-      ```
+      ```bicep
       resource cache 'Radius.Data/redisCaches@2025-08-01-preview' = {
         name: 'redis'
         properties: {
@@ -20,7 +20,7 @@ types:
 
       To connect your container to the cache, create a connection from the
       Container resource to the cache as shown below.
-      ```
+      ```bicep
       resource frontend 'Radius.Compute/containers@2025-08-01-preview' = {
         name: 'frontend'
         properties: {