Behavior of CommerceIdProvider#format is now controlled via commerce adapter metadata

The behavior of CommerceIdProvider#format is now controlled via commerce adapter metadata. The method creates tech Ids only if the commerce adapter service's additional metadata flag allow-tech-ids is set to true . The flag can be configured by setting the property metadata.additional-metadata.allow-tech-ids on the commerce adapter side.

Just a few commerce systems (like HCL) distinguish tech Ids from external Ids. If the commerce system does not distinguish tech Ids from external Ids, then both kinds of Ids can be used interchangeably but this leads to unnecessary cache misses, commerce communication and memory consumption in the CAE and commerce adapter caches. Projects running a HCL setup should use the configuration metadata.additional-metadata.allow-tech-ids so that the behavior of CommerceIdProvider#format matches the ID format passed from the HCL system to the CAE.

(CMS-20051)

Mimetype of uploaded xpi files is now recognized as application/x-xpinstall

Prior to the fix they have been recognized as application/zip.

(CMS-19951)

Reject requests against Studio Server until the application is live and ready

Depending on the deployment circumstances, Studio Server may have accepted requests before the application was live and ready. This lead to broken JSON responses and broken studio client sessions. This bug has been fixed by adding a filter that rejects requests during Studio startup and permits requests when Studio is live and ready.

(CMS-19589)

Fixed initialization of Studio ObjectMapper

Fixed a bug that caused the Studio ObjectMapper to get initialized without the DateSerializer required by the Studio Client under rare conditions.

(CMS-19582)