Synchronize Layer Upgrade Differences with ATT&CK Changelog Types

In April 2023, ATT&CK updated the types of changes it tracks (https://attack.mitre.org/resources/updates/updates-april-2023/) to break out "Changes" and "Minor Changes" into the following categories

• Major version changes: ATT&CK objects that have a major version change. (e.g., 1.0 → 2.0)
• Minor version changes: ATT&CK objects that have a minor version change. (e.g., 1.0 → 1.1)
• Other version changes: ATT&CK objects that have a version change of any other kind. (e.g. 1.0 → 1.2)
• Patches: ATT&CK objects that have been patched while keeping the version the same. (e.g., 1.0 → 1.0 but something like a typo, a URL, or some metadata was fixed)

Workbench is going to update to follow this convention soon. Navigator should follow suit.

https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/562

Example

This is what the Navigator looks like currently when upgrading a layer file

Start with the Navigator's current layer-file upgrade flow and compare its displayed difference types with the ATT&CK April 2023 update. Read the linked Workbench issue for the related convention. Done means the upgrade view distinguishes major, minor, other, and patch changes consistently with that convention.