Set annotation value ... only works if the property is already there

[MBcode]

Describe the bug
Set annotation value, only seems to reset values when the property is already there, but not add one (as it says it will) when the property was not there

To Reproduce
Steps to reproduce the behavior:

1. Go to Classes tab
2. Highlight any number of classes
3. Right click and choose: Set annotation value ...
4. Pick an annotation that is not already there, and a value
5. Click on the 'Set annotation value' button
6. When the 'Set annotation value Commit Message' comes up, hit the Continue button

Expected behavior
The value that was just set under that property should show up in all the highlighted
It completes without any error message in the web ui or in the local server logs, but only sets the value if the property was already there

Screenshots
If it helps I can add one, trying to add a new annotation property value pair to 2 classes in the pizza ontology

Desktop (please complete the following information):

• OS: local Linux server &the public server
• Browsers chrome and edge
• Version latest (4.0.2) on local server and on the public server, but not a problem in 4.0.1

Additional context
The first popup's description ends with: ".. If an entity does not currently have an annotation on the specific property then one will be created." but this is not the case

[MBcode]

Xendat Data & Analytics ontology team on assignment at Vertex pharmaceuticals and in collaboration with their Data and Software Engineering organization was able to produce a fix for the problem where Annotation values were not being set properly, as described in this incident. We provided a new, repaired version of SetAnnotationValueActionChangeListGenerator.java, and updated docker settings. We then ran a successful test to demonstrate that Annotation values are now being properly set.