[Bug]: NetworkType.CONNECTED constraint blocks offline background execution

### Current Behavior

Another issue from me.

There is no need to blocking background runner from starting when there is no internet connection or when the app has no internet permission. There is tons of use cases for bg runner without the internet.
If there is no internet, the task invoked by the runner should handle it, not the runner.

### Expected Behavior

Background task can be invoked without internet conneciton.

### Reproduction

https://github.com/ionic-team/capacitor-background-runner/tree/c07bf57773b6edef46b48e88e0a485a296b4899a/apps/example-app

### Screenshots / Media

_No response_

### Environment Details

```Shell
NA
```

### Versions Affected

latest

### Platforms Affected

- [ ] iOS
- [x] Android
- [ ] Web

### Notes / Comments

_No response_

Run the Android example app from the linked reproduction at commit c07bf57773b6edef46b48e88e0a485a296b4899a and observe background execution without an internet connection or permission. Read the Android background-runner path that applies the NetworkType.CONNECTED constraint. Done means the background task can be invoked offline, leaving internet handling to the task itself.

Written by the indexing model from the issue text.