Multiple dbus addresses used for accessing keyring

Question

When codex tries to access keyring, it seems to create a new dbus everytime from the same process. And codex seems to access keyrings a lot of times when using `chatgpt` auth mode.

Ideally the process should maintain its initially created bus and reuse it to access the keyring.

This can create an issue where the keyring service depends on explicit permission from user, and the dbus spam causes access-permission spam.

It happens for keepassxc which is a bug. But codex should still fix its dbus