Switch from monty to orjson for serialization

[munrojm]

This PR switches to using orjson for custom serialization in ReadOnlyResource.

[codecov]

Codecov Report

Merging #464 (5a67d79) into main (1348a1e) will decrease coverage by 0.16%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #464      +/-   ##
==========================================
- Coverage   88.42%   88.25%   -0.17%     
==========================================
  Files          40       40              
  Lines        2626     2631       +5     
==========================================
  Hits         2322     2322              
- Misses        304      309       +5     

Impacted Files	Coverage Δ
src/maggma/api/resource/read_resource.py	98.64% <100.00%> (ø)
src/maggma/api/utils.py	97.05% <100.00%> (+0.23%)	⬆️
src/maggma/stores/mongolike.py	82.19% <0.00%> (-1.90%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8122d6b...5a67d79. Read the comment docs.

[lgtm-com]

This pull request introduces 1 alert when merging 678d3bb into 8122d6b - view on LGTM.com

new alerts:

• 1 for Unused import

[shyamd]

Why orjson?

It seems silly, but can you add a test for custom_serialization. Maybe rename in object_id_serilaization_helper to make it clearer what it is doing?

Also, should the flag in ReadOnlyResource be called something different like disable_validation?

[munrojm]

orjson is extremely fast and can handle datetime object natively while allowing for extensions for things like bson types.

I have renamed things as you have suggested and added the test.