Upgrade improvements, removed usage of fromVersion parameter

[ShvaykaD]

Pull Request description

Removed old (not supported) upgrades.

For Customers:

• The --fromVersion parameter is no longer required in upgrade scripts. Upgrades now automatically start from the version currently set in your database.
• Added validation for DB version. If your database version is not compatible with the current upgrade, you will see the following message in the logs:

• Added validation for redundant upgrades: If you attempt to upgrade a database that is already up-to-date, you will see the following message in the logs:

Note: If you need to force an upgrade, you can bypass this validation by setting the SKIP_SCHEMA_VERSION_CHECK environment variable to true.

For Developers:

• You no longer need to manually set the schema version during installation or upgrades.
• New tables or indexes should be added directly to schema-entities.sql or schema-entities-idx.sql rather than the upgrade SQL file.
• Empty upgrade SQL files are no longer required in the upgrade directory. The logic now skips execution for non-existent SQL upgrade files.

General checklist

• You have reviewed the guidelines document.
• Labels that classify your pull request have been added.
• The milestone is specified and corresponds to fix version.
• Description references specific issue.
• Description contains human-readable scope of changes.
• Description contains brief notes about what needs to be added to the documentation.
• No merge conflicts, commented blocks of code, code formatting issues.
• Changes are backward compatible or upgrade script is provided.

Front-End feature checklist

• Screenshots with affected component(s) are added. The best option is to provide 2 screens: before and after changes;
• If you change the widget or other API, ensure it is backward-compatible or upgrade script is present.

Back-End feature checklist

• Added corresponding unit and/or integration test(s). Provide written explanation in the PR description if you have failed to add tests.
• If new dependency was added: the dependency tree is checked for conflicts.