fix(atomic): fix atomic react rendering function

[olamothe]

Couple seems to have went wrong:

• With the bump to [email protected], I also bumped some cra dependencies. This caused subtle changes to jest setup in headless-react samples, which means we now have to add extra config for Jest
• setRenderingFunction in AtomicResultList could be undefined if called before initialize. I modified it so that ResultListCommon is always created first, no matter the entry point.

🤞

https://coveord.atlassian.net/browse/KIT-1557

[github-actions]

Thanks for your contribution @olamothe !
When your pull-request is ready to be merged, check the box below to merge it

• Merge!

[github-actions]

Pull Request Report

PR Title

✅ Title follows the conventional commit spec.

Bundle Size

File	Old (kb)	New (kb)	Change (%)
case-assist	195.1	195.1	0
search	274	274	0
product-listing	207.8	207.8	0
product-recommendation	191.4	191.4	0
recommendation	190.1	190.1	0

[olamothe]

🤔 I might need to perform a "manual" publish of some packages to fix everything

[liviarett]

I'm just a bit confused by this, because ResultListCommon needs this.bindings, which only becomes available after initialize, so how can it be done independently?

[olamothe]

I'm just a bit confused by this, because ResultListCommon needs this.bindings, which only becomes available after initialize, so how can it be done independently?

The initialize function is part of Atomic lifecyle (ie: we control when it's called, with the search interface).

Which means it is possible for any code interacting with our components to call any public function on any component. before we internally have a chance to call initialize.