Handle case when Sensei is updated from a very old Sensei version

[fjorgemota]

Is your feature request related to a problem? Please describe

If a user from a very old Sensei version decides to update to the very latest version, the update is proceeded successfully.

However, because on 25606d0215399860d58766123e119c5b91b19abb we deleted all the legacy data updates, the user might not have a smooth experience because, officially, the minimum Sensei version we're able to update from is the 3.0.0, released on 2020.

Describe the solution you'd like

I'd like Sensei to throw an error when it detects such an old version, in such a way that the update process is blocked and the user can migrate to the "intermediate" versions before jumping to the very latest version.

Describe alternatives you've considered

Adding this tip on the documentation, but, honestly, considering how easy WordPress allows users to update to the very latest version of a plugin, I'm not sure if it would be effective.

Additional context

Possibly affected user on ticket 7089341-zd-a8c

[github-actions[bot]]

Support References

This comment is automatically generated. Please do not edit it.

• [ ] 7089341-zen

[donnapep]

Marking this as low priority as this should be a very infrequent occurrence.