[Bug]: Running `container image push` after `container registry login` requires keychain access

### I have done the following

- [x] I have searched the existing issues
- [ ] If possible, I've reproduced the issue using the 'main' branch of this project

### Steps to reproduce

After `container registry login`, trying to push that image requires keychain access.

The keychain entry is made for the `container` appliation, but `container-core-images` requires access to the keychain item to run.

### Current behavior

Popup dialogue `container-core-images is requesting access to the xxx secret`

Having keychain ask every time is inconvenient when scripting and needing to re login to the registry every 12 hours with AWS ECR.

Clicking allow all is possible - but when using short lived credentials doesn't help since the credential gets re-made on each `registry login`

### Expected behavior

The `container` application already has access to the keychain item, so it would be great if `container-core-images` also had access by default.

### Environment

```markdown
- OS: macOS 26.2
- Xcode: Version 26.2
- Container: 0.9.0
```

### Relevant log output

```shell
N/A
```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct