don't fail when a dependency doesn't have a previous version

[jakecoffman]

What are you trying to accomplish?

In #9888 I moved the failure out of the service and into the Updater.

In this PR, I prevent the failure by removing the questionable update, and logging to tell us what's happening.

It seems there are various reasons why an update with no previous version will happen, but rather than failing the job or a group, we should log it and continue on.

Anything you want to highlight for special attention from reviewers?

How will you know you've accomplished your goal?

We should stop seeing the error being reported.

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[jakecoffman]

I reran a job that previously errored and it didn't error this time, so this is working.