Upgrade notifications are sent even when no direct upgrade path is available
A new version notification is sent to users even when no direct path is available from their currently deployed version to the new version. For example:
- Current version is: 3.5.2
- Next available version is: 3.5.9 (available in the catalog, but the user has chosen not to upgrade yet. A notification has been sent when 3.5.9 was made available in the catalog, which is the correct behavior)
- New version is: 3.6.8 - the user is notified that 3.6.8 has been added and is invited to upgrade, even though they must first upgrade to 3.5.9.
NMaaS currently only supports linear version upgrades, so the user cannot directly upgrade from 3.5.2 to 3.6.8. We should revise whether an explicit notification is needed to be sent in such cases.