Handle configuration triggered errors on UPS creation on completion of previous UPS gracefully

[vrindanayak]

Rationale : If archive is configured to create a new UPS on completion of a previous UPS using a configured UPS on UPS Completed rule, with following configs

• Include Input Information set to default COPY_OUTPUT
• Include Referenced Request set to True

and, Change Workitem State is invoked, wherein the UPS whose state is being changed to COMPLETED does not contain Output Information Sequence and / or Referenced Request Sequence, the service throws

< HTTP/1.1 500 Internal Server Error
< Access-Control-Allow-Headers: origin, content-type, accept, authorization
< Warning: 299 http://localhost:8880/dcm4chee-arc/aets/DCM4CHEE/rs/workitems: java.lang.NullPointerException

even if previous UPS state was successfully changed to COMPLETED

Instead, improve the behaviour by logging the information of incorrect configuration and state of attributes of previous UPS, allowing the invoked service to return 200 - Ok for successful state change of previous UPS to COMPLETED.