Tokens specifically for Remote KV without access to everything else that a PAT allows

### What problem are you trying to solve?

Minimizing the scope of allowed actions on a Personal Access Token

### Describe the solution you'd like

Does the Deploy team plan on having alternate ways to authorize connecting to a Remote KV ?? It would be great to have a way to do that without having to use a PAT that also has access to do a bunch of other things like deploy your code, etc. Maybe like a way to just generate keys specifically for KV connections

### Describe alternatives you've considered

N/A

### Documentation, Adoption, Migration Strategy

_No response_