Damage should not result in an immediate run

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Package ecosystem

All.

### Package manager version

_No response_

### Language version

_No response_

### Manifest location and content before the Dependabot update

_No response_

### dependabot.yml content

_No response_

### Updated dependency

_No response_

### What you expected to see, versus what you actually saw

Damaging the dependabot file (modification) results in am immediate run. This includes a simple schedule change, which is not ideal. Once the file is committed, having a GUI element to rerun or similar is the correct behaviour to move forward for current consumers.

### Native package manager behavior

_No response_

### Images of the diff or a link to the PR, issue, or logs

https://github.com/autobrr/autobrr/pull/1042

### Smallest manifest that reproduces the issue

I'm happy to connect with the PM or similar if that's desirable during ET working hours.

Start by reviewing the behavior described for modifications to dependabot.yml and the referenced autobrr/autobrr pull request 1042. Trace where configuration changes trigger a run, then identify the relevant tests or entry points; done means a committed schedule change no longer causes an immediate run and the documented rerun path works.

Written by the indexing model from the issue text.