chore: move proxy and old konnectors to archive

docs/konnectors/enedis.md → docs/archive/enedis.md

 # Enedis Konnector
 
 :::warning DEPRECATED
-This section of documentation is not relevant anymore, enedis data connect has been replaced with [enedis sge](./enedis-sge.md)
+This section of documentation is not relevant anymore, enedis data connect has been replaced with [enedis sge](../konnectors/enedis-sge.md)
 :::
 
 This konnector fetches consumption measures from Enedis API. This is an Oauth Konnector, meaning the authentication performed to access all data is made following an Oauth2 protocol.
@@ -12,12 +12,12 @@ You should also check Cozy's official documentations for konnectors :
 - https://docs.cozy.io/en/tutorials/konnector/getting-started
 - https://docs.cozy.io/en/tutorials/konnector/oauth/
 
-The Oauth protocol does not take place in the konnector code, therefore it is also important to take a look at the [proxy](/docs/proxy/description) documentation to fully understand all the interactions that will be told below.
+The Oauth protocol does not take place in the konnector code, therefore it is also important to take a look at the [proxy](/docs/archive/proxy) documentation to fully understand all the interactions that will be told below.
 
 All the actions performed by the stack are targeted from pre-registered parameters, here is the list of all parameters needed by the stack to perform the Oauth protocol and allow the konnector to fetch data.
 On its first launch, following the Oauth Client Connect authentication.
 
-- The cozy stack calls the **authentication_endpoint** and start the oauth protocol, see [proxy doc](/docs/proxy/description).
+- The cozy stack calls the **authentication_endpoint** and start the oauth protocol, see [proxy doc](/docs/archive/proxy).
 - The account has now an access_token and an id_token from the oauth call
 
 :::info

docs/konnectors/grdf.md → docs/archive/grdf.md

 # GRDF Client Connect Konnector
 
 :::warning DEPRECATED
-This section of documentation is not relevant anymore, grdf client connect has been replaced with [grdf tier direct](./grdf-td.md)
+This section of documentation is not relevant anymore, grdf client connect has been replaced with [grdf tier direct](../konnectors/grdf-td.md)
 :::
 
 This konnector fetches consumption measures from Grdf Adict API. This is an Oauth Konnector, meaning the authentication performed to access all data is made following an Oauth2 protocol.
@@ -12,7 +12,7 @@ You should also check Cozy's official documentations for konnectors :
 - https://docs.cozy.io/en/tutorials/konnector/getting-started/
 - https://docs.cozy.io/en/tutorials/konnector/oauth/
 
-The Oauth protocol does not take place in the konnector code, therefore it is also important to take a look at the [proxy](/docs/proxy/description) documentation to fully understand all the interactions that will be told below.
+The Oauth protocol does not take place in the konnector code, therefore it is also important to take a look at the [proxy](/docs/archive/proxy) documentation to fully understand all the interactions that will be told below.
 
 All the actions performed by the stack are targeted from pre-registered parameters, here is the list of all parameters needed by the stack to perform the Oauth protocol and allow the konnector to fetch data.
 
@@ -20,7 +20,7 @@ All the actions performed by the stack are targeted from pre-registered paramete
 
 On its first launch, following the Oauth Client Connect authentication.
 
-- The cozy stack calls the **authentication_endpoint** and start the oauth protocol, see [proxy doc](/docs/proxy/description).
+- The cozy stack calls the **authentication_endpoint** and start the oauth protocol, see [proxy doc](/docs/archive/proxy).
 - The account has now an access_token and an id_token from the oauth call
 
 :::note