Fix missing images on English pages

Hugo only auto-shares page-bundle resources across translations when
each language has its own content directory; with filename-based
translation (index.fr.md / index.en.md in the same folder) a resource
with no language code is assigned to the default language only. Add
.en.-suffixed copies of every image referenced from English pages and
point the English markdown at them.

content/documentation/devpod/_index.en.md

@@ -66,11 +66,11 @@ In my day-to-day networking adventures, I deploy ContainerLab-based setups with
 
 DevPod uses **Providers**, which are configuration modules that define where and how DevPod launches your environment. Here's the list of providers:
 
-![Provider_list](provider.fr.png#center)
+![Provider_list](provider.en.png#center)
 
 We're going to focus on the **AWS Provider** — even though there are plenty of configuration options:
 
-![Provider_list](aws_options.fr.png#center)
+![Provider_list](aws_options.en.png#center)
 
 Before you panic at all these settings, don't worry. If you're just doing a bit of experimenting, the default values will usually do the job. 🙌
 
@@ -245,7 +245,7 @@ Go back to **Users** → **devpod-tool-user** → **Permissions** to confirm tha
 
 - If you created a programmatic user, make sure to note down the **Access Key ID** and the **Secret Access Key**.
 
-![devpod_user_sumup](devpod_user.fr.png#center)
+![devpod_user_sumup](devpod_user.en.png#center)
 
 **Bonus**: Note your **VPC ID** (in the VPC section on AWS). You'll need it when configuring DevPod.
 
@@ -277,7 +277,7 @@ When prompted for:
 
 Click **Add Provider**.
 
-![added_new_provider](new_provider.fr.png#center)
+![added_new_provider](new_provider.en.png#center)
 
 ## Testing a deployment 🧪
 
@@ -292,23 +292,23 @@ Let's do a quick test using one of the pre-built Docker images:
 5. On the right, select a quick-start example (e.g., Python). 🐍
 6. Click **Create Workspace**.
 
-![new_worspace](new_worskapce.fr.png#center)
+![new_worspace](new_worskapce.en.png#center)
 
 Wait a few moments, and your cloud-based environment will pop up in VS Code. 🎊
 
-![vscode](vscode.fr.png#center)
+![vscode](vscode.en.png#center)
 
 ### Stop
 
 When you're not using the environment, click **Stop** to shut down the EC2 instance. You'll only pay for storage — no compute time. Great for your wallet. 💰
 
-![Stopped Instance](stopped_instance.fr.png#center)
+![Stopped Instance](stopped_instance.en.png#center)
 
 ### Delete
 
 Deleting the workspace removes all AWS resources associated with that environment, so you won't pay a dime. But you'll need to redeploy if you want to use it again. ♻️
 
-![Delete Instance](delete_instance.fr.png#center)
+![Delete Instance](delete_instance.en.png#center)
 
 ## Conclusion 💡