fix: submit form after formik values are saved

[oxaudo]

Attempting to fix: EMI-2376

After some digging and pointers from @erikdstock seems like the issue is that submit form is called before formik.setValues finished executing. And seems like setValues doesn't return a promise, awaiting it doesn't ensure the values are updated. - so trying to use useEffect with a dependency on formikContext.values instead when address is saved.

Seems to fix this concrete error but not sure it does not break something else :( Did some local testing and seems fine though....

[relativeci]

#2354 Bundle Size — 8.74MiB (-0.31%).

8ab6114(current) vs 980b7ae main#2351(baseline)

Warning

Bundle contains 18 duplicate packages – View duplicate packages

Bundle metrics   8 changes 1 regression 2 improvements

	Current #2354	Baseline #2351
Initial JS	3.55MiB(-0.7%)	3.58MiB
Initial CSS	0B	0B
Cache Invalidation	48.16%	40.94%
Chunks	101(-0.98%)	102
Assets	104(-0.95%)	105
Modules	5743(+0.05%)	5740
Duplicate Modules	524(+1.35%)	517
Duplicate Code	4.08%(+1.49%)	4.02%
Packages	269(-0.74%)	271
Duplicate Packages	17	17

Bundle size by type   2 changes 2 improvements

	Current #2354	Baseline #2351
JS	8.6MiB (-0.3%)	8.63MiB
Other	141.62KiB (-0.83%)	142.8KiB

Bundle analysis report Branch oxaudo/address Project dashboard

---

^{Generated by RelativeCI Documentation Report issue}

[erikdstock]

And seems like setValues doesn't return a promise, awaiting it doesn't ensure the values are updated. - so trying to use useEffect with a dependency on formikContext.values instead when address is saved.

setValues() does return a promise but we could confirm it with our version of formik. I don't see what difference this code would make in that issue except that adding some extra useState + useEffect will add some more async magic that might be waiting long enough. TLDR I think that if this works it is by luck and we are hacking around some deeper problem. Maybe with the upcoming work we have that is enough for a short-term fix. Interested in others' thoughts.

I do see that the setValues call will also call the validation logic - i wonder if something could be going wrong in a way we don't see with the nested saved addresses form values going into the fulfillment details context.

[oxaudo]

I'm going to merge this one and see how it performs. Any objections?