Devcointainer and docs update (openwallet-foundation#3629)

Author: esune

.devcontainer/devcontainer.json

@@ -39,8 +39,7 @@
                     "enable": true
                 },
                 "ruff.fixAll": true,
-                "ruff.format.args": ["--config=./pyproject.toml"],
-                "ruff.lint.args": ["--config=./pyproject.toml"]
+                "ruff.configuration": "~/.config/pyproject.toml"
             }
         }
     },

docs/deploying/AnoncredsControllerMigration.md

@@ -653,7 +653,7 @@ to
 
 The upgrade endpoint is at **POST /anoncreds/wallet/upgrade**.
 
-You need to be careful doing this, as there is no way to downgrade the wallet. It is recommended highly recommended to back-up any wallets and to test the upgrade in a development environment before upgrading a production wallet.
+You need to be careful doing this, as there is no way to downgrade the wallet. It is highly recommended to back-up any wallets and to test the upgrade in a development environment before upgrading a production wallet.
 
 Params: `wallet_name` is the name of the wallet to upgrade. Used to prevent accidental upgrades.
 
@@ -670,6 +670,8 @@ The agent will get a 503 error during the upgrade process. Any agent instance wi
 
 The aca-py agent will work after the restart. However, it will receive a warning for having the wrong wallet type configured. It is recommended to change the `wallet-type` to `askar-anoncreds` in the agent configuration file or start-up command.
 
+**Note:** when in a multitenant mode, it is recommended to upgrade the admin wallet *before* the sub-wallets, as this will ensire new sub-wallets will be created using the `askar-anoncreds` wallet type. In order to invoke the upgrade endpoint for the admin wallet, the path `/anoncreds/wallet/upgrade` muse be "enabled" by adding it to the `base-wallet-paths` setting.
+
 ### Subwallet (tenant) in multitenancy mode
 
-The sub-tenant which is in the process of being upgraded will get a 503 error during the upgrade process. All other sub-tenants will continue to operate normally. After the upgrade is complete the sub-tenant will be able to use the new endpoints. The old endpoints will no longer be available and result in a 403 error. Any aca-py agents will remain running after the upgrade and it's not required that the aca-py agent restarts. 
+The sub-tenant which is in the process of being upgraded will get a 503 error during the upgrade process. All other sub-tenants will continue to operate normally. After the upgrade is complete the sub-tenant will be able to use the new endpoints. The old endpoints will no longer be available and result in a 403 error. Any aca-py agents will remain running after the upgrade and it's not required that the aca-py agent restarts.