format: fix codeblocks without language

After updating the builder container for our website,
we have some formatting issues when we use a codeblock that doesn't
explicitly specify a language.

Update some of these blocks to fix.

Signed-off-by: Tobin Feldman-Fitzthum <tfeldmanfitz@nvidia.com>

Author: fitzthum

content/en/docs/contributing/_index.md

@@ -100,7 +100,7 @@ Every PR in every subproject is required to include a DCO.
 This is strictly enforced by the CI.
 Fortunately, it's easy to comply with this requirement.
 At the end of the commit message for each of your commits add something like
-```
+```bash
 Signed-off-by: Alex Ample <al@example.com>
 ```
 You can add additional tags to credit other developers who worked on a commit
@@ -143,7 +143,7 @@ what it does.
 This helps reviewers and future developers.
 
 The title of the commit should start with a subsystem. For example,
-```
+```bash
 docs: update contributor guide
 ```
 The "subsystem" describes the area of the code that the change applies to.

content/en/docs/features/get-attestation.md

@@ -25,7 +25,7 @@ agent.guest_components_rest_api=all
 ```
 
 As usual, command line configurations can be added with annotations.
-```
+```yaml
 apiVersion: apps/v1
 kind: Deployment
 metadata:

content/en/docs/troubleshooting/_index.md

@@ -28,7 +28,7 @@ Sometimes this will give you a useful message pointing to a failed attestation
 or some sort of missing environment setup. Most of the time you will see a
 generic message such as the following:
 
-```
+```bash
 Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: failed to create shim: Failed to Check if grpc server is working: rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 637456061:1024: unknown
 ```
 
@@ -111,7 +111,7 @@ or hope that Kubernetes restarts your existing pod. Note that enabling debug opt
 config file can change the attestation evidence of a confidential guest.
 
 Now you should be able to view logs from containerd with the following:
-```
+```bash
 sudo journalctl -xeu containerd
 ```
 
@@ -179,7 +179,7 @@ you want to access. Do this via `ps -ef | grep qemu` or equivalent.
 The id is the long id that shows up in many different arguments.
 It should look like `1a9ab65be63b8b03dfd0c75036d27f0ed09eab38abb45337fea83acd3cd7bacd`.
 Once you have the id, you can use it to access the debug console.
-```
+```bash
 sudo /opt/confidential-containers/bin/kata-runtime exec <id>
 ```
 You might need to symlink the appropriate Kata configuration file for your runtime
@@ -238,7 +238,7 @@ If your CoCo Pod gets an error like the one shown below, then it is likely the i
 
 Therefore, you must ensure that the image pull policy is set to **Always** for any CoCo pod. This way the images are always handled entirely by the agent inside the VM. It is worth mentioning we recognize that this behavior is sub-optimal, so the community provides solutions to avoid constant image downloads for each workload.
 
-```
+```bash
 Events:
   Type     Reason     Age               From               Message
   ----     ------     ----              ----               -------