Issue 475: Alphabetic follow up, addressing more management fields.

[kaladay]

Description

There are additional management fields that are not alphabetically sorted that were missed in the previous PR (#486).

There are two cases where I opted to perform the sorting on the back-end. The metadaum and operators. On the UI side, both of these are either validatedinput or multi-suggestion-input fields. I do not see any obvious support in weaver-ui-core that supports the sorting on the list. Therefore, I opted to sort on the back-end. I used the DB order for InternalMetadata. I used the Java array string sort for the Operator given the current design.

The type aheads on the Readers have the UI orderBy filter added. The Reader Field Mappings could also have additional sorting, but this requires more discussion and is omitted.

Fixes #475

Type of change

• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [X] Manual testing.

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] My changes generate no new warnings
• [x] New and existing unit tests pass locally with my changes

[coveralls]

Coverage: 45.24% (+0.03%) from 45.215% when pulling 2a8a99400f568e6252815387992d7fa61a157d14 on 475-alphabetic into 850bc32a56746c6318594867a67475340d5b7b62 on staging.