AccessToken is always stored in global config below the IMS context

When using a local `.aio` config file similar to what is outlined in https://github.com/adobe/aio-cli-plugin-cloudmanager?tab=readme-ov-file#setup-for-oauth-integration with `aio config:set ims.contexts.aio-cli-plugin-cloudmanager PATH_TO_CONFIG_JSON_FILE --file --json --local` I expect that the accessToken which is retrieved is also stored locally, however this is persisted in the global aio config due to https://github.com/adobe/aio-lib-ims/issues/67 like this.

```
ims: {
contexts: {
aio-cli-plugin-cloudmanager: {
...
// duplicated service credentials from the local .aoi file
...
access_token: {
token: ",
expiry: ...
}
},
```

In order to be able to easily switch between different credentials/organization just using the local AIO config (https://github.com/adobe/aio-lib-core-config/tree/master?tab=readme-ov-file#project-configuration) is not enough. Instead one currently has to use dedicated/unique IMS context names and always pass that via `imsContextName` to each `aio cloudmanager` command as workaround.

Please document that limitation in the readme and try to fix the upstream bug in https://github.com/adobe/aio-lib-ims/issues/67.

Comienza con la sección de configuración de la README enlazada en el issue y reproduce la configuración local de `.aio` con el contexto de Cloud Manager IMS. Revisa el issue upstream #67 de `aio-lib-ims` para entender la persistencia global del token; después, documenta la limitación y determina el fix upstream necesario; se considera terminado cuando las credenciales locales ya no persistan globalmente o la limitación esté claramente documentada.

Escrito por el modelo de indexación a partir del texto del issue.