fix(awe-builder): align builder action names and dead XSD values with the client contract

The screen contract has values that no client engine understands:

The builder enum Action emits check-records-selected for CHECK_RECORDS_GENERATED (the contract value is check-records-generated), and select-first-rows / select-last-rows for SELECT_FIRST_ROW / SELECT_LAST_ROW (the contract values are singular) (awe-builder Action.java:24,60-61). Java code that uses these builders sends actions that neither engine handles.
XSD values with no behaviour in either engine: forward, check-leaf-selected, check-parent-expanded, get-locals; the elements frame and javascript; the criteria component progress.
The AngularJS engine has no handler for toggle-class, which the XSD and the builder offer (the React engine handles it).
The React engine registers targetMessage while the contract name is target-message.

Every value the builders emit is a value of the contract, and every value of the contract is handled by both engines or removed from it (with a deprecation note in the migration guide).

The builder enum emits the contract values (tests)
A decision for each dead XSD value: implemented in both engines, or deprecated and removed
toggle-class handled by the AngularJS engine, or removed
A test compares the XSD values, the builder values and the actions handled by each engine (with #810)