fix: Do not evaluate isClassArityUsageDisabled on every serialize/des…

[s-gelazevicius]

…erialize function call

I noticed degraded performance after upgrading to new version.
isClassArityUsageDisabled was evaluated on every serialize/deserialize function call.
This is quite expensive because map is created every time, then get and exist is called.
This can be observed in attached flamegraph:

[novakov-alexey]

@s-gelazevicius thank you for this PR.

Maybe even move that value into the object CaseClassSerializer, since it is just env variable check which can be checked on startup?

[s-gelazevicius]

@s-gelazevicius thank you for this PR.

Maybe even move that value into the object CaseClassSerializer, since it is just env variable check which can be checked on startup?

Done.

[s-gelazevicius]

@novakov-alexey Thank you for quick response, maybe you know when new version with a fix can be released

[novakov-alexey]

@s-gelazevicius I think I will release it today.