Give user registered types priority when encoding / decoding JSON

[soceanainn]

User registered types should take priority over default types in Kombu.

Although users can currently override the encoder/decoder for a Kombu registered type by calling register_type (for example calling register_type(Decimal, ...) in their own code), this doesn't work well when it comes to subclassing. If users currently need to pass subclasses of any Celery registered types (datetime, date, time, Decimal or UUID) they would be forced to either:

1. Override implementation of superclass with a subclass aware encoder / decoder implementation, or
2. Access the 'protected' _encoders dictionary in the Kombu json module, pop the value for the superclass, add their subclass, and then re-add the superclass.

By separating user registered types and Kombu registered types into separate dictionaries, we can always give priority to user registered types instead, which simplifies this process for users (although technically it is a breaking change from existing behaviour).

Solves #1895

[codecov]

Codecov Report

Attention: Patch coverage is 95.65217% with 1 line in your changes missing coverage. Please review.

Project coverage is 81.51%. Comparing base (c5e25d2) to head (7a20cbd).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
kombu/utils/json.py	95.65%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2188      +/-   ##
==========================================
+ Coverage   81.50%   81.51%   +0.01%     
==========================================
  Files          77       77              
  Lines        9522     9533      +11     
  Branches     1151     1156       +5     
==========================================
+ Hits         7761     7771      +10     
  Misses       1569     1569              
- Partials      192      193       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[auvipy]

please fix the lint errors as well

[Nusnus]

I briefly reviewed the PR and it looks nice but I wonder if anything might break due to the split, even though it makes sense.

[auvipy]

I briefly reviewed the PR and it looks nice but I wonder if anything might break due to the split, even though it makes sense.

technically the change is a breaking change

[auvipy]

we have to release in in a new major version like 5.5/5.6