continuous-deploy-fingerprint starts new build when the matching build is expired

### Description of the bug
We are using `continuous-deploy-fingerprint` and noticed the last deployment it started a new production build even though no native changes were made. We checked the fingerprint reported by the gh action and was able to match a build, but later noticed that the build is expired. This is the only thing we noticed as the possible cause, expired builds should not matter for OTA updates and should not trigger a store release.

### To Reproduce
started a new GitHub action using expo/expo-github-action/continuous-deploy-fingerprint@main

#### Expected behavior
Over the air update should've happen

#### Actual behavior
Started a new production build and store submission.

Output from the action:

```
No existing iOS build found for fingerprint, starting a new build...
No existing Android build found for fingerprint, starting a new build...
```