Command Expansion bulk compatibility check

winner
https://jira.jpl.nasa.gov/browse/AERIEQS-374
Moderate
The original use case had been discussed before the concept of an expansion set had been created, but I think being able to perform this comparison action against an entire set at once would meet the need.

We can kind of do this on a one-by-one basis in the editor, but it is tedious and not good for bulk updates (such as the delivery of a new command dictionary or model) that will make up the majority of use cases during operations. Being able to bulk check compatibility would reduce the likelihood of errors in operations stemming from an incompatible command expansion.

The payload names no files or tests; start by reading the linked JIRA request and locating the editor's existing one-by-one compatibility check. Done means the same comparison can be performed for an entire expansion set, supporting bulk updates without requiring each item to be checked manually.