SSP-2702 Fully populate client-side Person singleton after Quick Add

It takes at least two API calls to fully create a server-side Person
as a side-effect of submitting the Quick Add form... one to
create the Person and one to assign a Program Status. Previously,
the response from the Person create was cached client side in the
singleton Person model prior to assigning the Program Status. The
Main tool no longer attempts to reload that Person, so Program
Status (and other fields) would potentially be rendered with stale
(empty) values.

This patch addresses the problem by always reloads the Person from
the server before dismissing the Quick Add dialog in the success path.