Code cleanup: The tangle of BindWizard classes is ugly

[emersonrp]

The nest of BindPane -> BindWizard-parent -> BindWizard -> WizardDialog plus maybe one or more other is extremely difficult to navigate. I blame me. The non-wx-object wizard class is probably the right place to apply pressure, either to absorb more of the functionality, or to parcel it out up and down and get out of the way. This is not super clear and it's going to be ugly to do but it'll make this much less of a headache later.

[emersonrp]

Re-examining this, I've remembered that the notion is to have the BindWizard object itself, the non-wx one, be the repository of state so we don't have to initialize a bunch of wx stuff at Profile load time, particularly the edit dialog. So, there's a method to the madness, but there is still some back-and-forth, now with the new ListPanel superclass, so ListPanel -> CustomBindPaneParent -> WizardBindPane, which has an instance of a subclass of WizardParent, which contains the UI and logic for the WizardBindPane and the WizardEditDialog. Oy.