Removed afterburner usage from Cosmos Exception

[kushagraThapar]

• Removed afterburner usage from Cosmos Exception
• Closes [BUG] Jackson afterburner warning messages are logged when first exception occurs #19847
• Closes [BUG]java.lang.IllegalAccessError on error log on starting #20088
• On investigating this more, the issue started happening on CosmosException after we converted the cosmos exception message into Json format in this PR : Converting cosmos exception into json format #18092 after release 4.11.0 and above.
• Currently just logging CosmosDiagnostics doesn't throw this warning, but when logging CosmosException, the warning is thrown, because CosmosException uses Utils.getSimpleObjectMapper() - which registers module AfterBurnerModule()

Utils.simpleObjectMapper.registerModule(new AfterburnerModule());

There is no need to use this same ObjectMapper for CosmosException, it can use its own ObjectMapper as used by CosmosDiagnostics, ClientSideRequestStatistics, ClientTelemetry, RntbdObjectMapper and so on.

[moderakh]

Thanks @kushagraThapar
LGTM.

[FabianMeiswinkel]

As discussed offline - I would prefer also renaming Utils.getSimpleObjectMapper to something like Utils.getObjectMapperWithAfterBurner to avoid unintentional regressions in the future.

Otherwise LGTM

[moderakh]

As discussed offline - I would prefer also renaming Utils.getSimpleObjectMapper to something like Utils.getObjectMapperWithAfterBurner to avoid unintentional regressions in the future.

Otherwise LGTM

can we maybe call it Utils.getObjectMapperForPayloadData() or something like that as it is intended to be used for serializing/deserializing data payload and afterburner is intended to optimize that code path only.

[xinlian12]

LGMT, thanks for the fix Kushagra

[kushagraThapar]

@FabianMeiswinkel @moderakh - I have updated the name to getObjectMapperForPayLoadData.

The reason I didn't choose objectMapperWithAfterBurner is because in near future if we register more modules to this objectmapper, then having afterBurner in the name might not justify the different modules this objectmapper refers to.
Let me know if this makes sense or not.