FIX - Reporting missing "property.type" XML/JSON property

[Agnul97]

the call to the rest-api endpoint PUT /{scopeId}/serviceConfigurations/{componentId} was returning a 204 code when some "properties" you want to update had a missing "type" parameter. This was wrong because, in this case, the back-end cannot unmarshall properly the xml/json, resulting in a no-up update, so an error should be shown to the client.

To change this, I modified the code of the custom unmarshaller we created (XmlPropertiesAdapter.java) in order to throw an internal exception in such case.

I tried to throw a more proper KapuaException instead of the internalError but I had some problems for the way JAXB handles exceptions. In a future PR I will work on this in order to more correctly propagate a 404 error code to the client

Finally, I added some tests

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 16.81%. Comparing base (ce975f4) to head (46bdeff).
Report is 7 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff             @@
##             develop    #4109   +/-   ##
==========================================
  Coverage      16.80%   16.81%           
  Complexity        22       22           
==========================================
  Files           2019     2019           
  Lines          52410    52411    +1     
  Branches        4417     4417           
==========================================
+ Hits            8810     8812    +2     
  Misses         43202    43202           
+ Partials         398      397    -1     

Files with missing lines	Coverage Δ
...kapua/model/xml/adapters/XmlPropertiesAdapter.java	97.43% <100.00%> (+0.06%)	⬆️

... and 1 file with indirect coverage changes