studio: Improve API Keys area to better understand where and how used

Feature Description

Recently, I needed to delete an API key. When I went into API Keys area of the Studio, I saw I had 8-10 keys dating back to late 2025.

I found it difficult to know:

• which keys were active (last used)
• if they expire/d (doesn't seem they do)
• the names were not meaningful nor did it match the name in the auth.json Command Code config settings
• I could not edit the name to make them meaningful to me
• recent usage of keys and where used (to identify if any key leaked and used by some strange IP address or geo)

So, I ended up just deleting all keys one by one and starting over from scratch, but then I realized:

• the name in auth.json did not match
• and the only way I could identify a key was by some UTC timestamp so I could tell one cli on one machine was an older key than another because I knew I created one before the other

Use Case

In general, be useful to:

• know which key used where
• add a description for the key purpose
• names match installed name in auth.json
• edit names to be descriptive
• show some recent use (time, IP address, geo) to identify if any leaks
• pause key
• rotate key (vs delete and create and edit name a description)

Could take some cues from Unkey API Key management features. See: https://www.unkey.com/docs/platform/apis/keys

Additional Context

No response

How important is this to you?

Medium. But, this will increase if I use Command Code API more for inference in apps vs just the cli used on two devices or if I want to distinguish between a key for cli and a key for desktop.

Comienza revisando el área de Studio API Keys y cómo se relacionan los nombres de las claves con la configuración de Command Code en auth.json. El issue describe varias capacidades posibles, por lo que es necesario acotar el alcance y los criterios de finalización antes de poder comenzar la implementación.