website: hardcode version banner for 0.1 docs

O.1 docs is deprecated. Let's inform user to switch the the latest version

Signed-off-by: user.email <jf@dagger.io>

docs/core-concepts/1203-client.md

@@ -1,6 +1,6 @@
 ---
 slug: /1203/client
-displayed_sidebar: europa
+displayed_sidebar: '0.2'
 ---
 
 # Interacting with the client
@@ -18,11 +18,13 @@ displayed_sidebar: europa
 You may need to load a local directory as a `dagger.#FS` type in your plan:
 
 ```cue file=../tests/core-concepts/client/plans/fs.cue
+
 ```
 
 It’s also easy to write a file locally:
 
 ```cue file=../tests/core-concepts/client/plans/file.cue
+
 ```
 
 ## Using a local socket
@@ -40,6 +42,7 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
 <TabItem value="unix" label="Linux/macOS">
 
 ```cue file=../tests/core-concepts/client/plans/unix.cue
+
 ```
 
 </TabItem>
@@ -47,6 +50,7 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
 <TabItem value="windows" label="Windows">
 
 ```cue file=../tests/core-concepts/client/plans/windows.cue
+
 ```
 
 </TabItem>
@@ -59,6 +63,7 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
 Environment variables can be read from the local machine as strings or secrets, just specify the type:
 
 ```cue file=../tests/core-concepts/client/plans/env.cue
+
 ```
 
 ## Running commands
@@ -66,6 +71,7 @@ Environment variables can be read from the local machine as strings or secrets,
 Sometimes you need something more advanced that only a local command can give you:
 
 ```cue file=../tests/core-concepts/client/plans/cmd.cue
+
 ```
 
 :::tip
@@ -77,4 +83,5 @@ You can also capture `stderr` for errors and provide `stdin` for input.
 If you need the current platform though, there’s a more portable way than running `uname` like in the previous example:
 
 ```cue file=../tests/core-concepts/client/plans/platform.cue
+
 ```