raise when an unsupported package manager version is present

[jakecoffman]

What are you trying to accomplish?

When we parse the manifest files, if we come across an unsupported package manager version, we should immediately fail the job.

The idea is the customer will need to upgrade or remove the old manifest to get updates again. This keeps our code simple to maintain rather than trying to work around old outdated versions.

Anything you want to highlight for special attention from reviewers?

Most of this PR is implementing it in the "silent" ecosystem which is a dummy ecosystem used to test the updater.

How will you know you've accomplished your goal?

This change will cause bundler 1 jobs to start failing with a clear error message.

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.

[kbukum1]

• Adding specs for update file commands
• Adding specs for dependency snapshots
• Removing unsupported package manager error from operations

[honeyankit]

LGTM