Better default workflow

This is what you get by clicking 'configure.'

The default workflow page quickly becomes usuable as modules are added. I think it works much better broken up into one page per content type. This is a very basic patch which simply moves around the UI and does not change any functionality.

I see lots of potential in following this path:
* The submission guidelines would make sense on this page. Have the node module put those in, no need to have it duplicated in all the modues.
* This page could be moved around to be a top level admin menu with local tasks 'list' and 'add new type' for making lightweight types on the fly instead of the very lightweight modules we have now.
* Permissions for who can create nodes or edit their own might make sense on or next to these pages.
* The various elements of the create content form, or even the node view, could be reordered with weights.

This requires modules implementing hook_nodeapi('settings') to return strings containing the form elements instead of associative arrays.

Here is a cleaned up patch which:
- Capitalizes the column headers
- Uses form_checkboxes() instead of the form_item() hack

Because I wanted to use form_checkboxes() rather than a form_group() I had to make those 5 variables into one array. There is an update to set the one variable per node type to the values of the five old ones, and delete the five. I have not benchmarked the difference of one array per node type in the variables table vs. five booleans (ints) per node type, but I expect it might be faster.

I do have more ideas for what should be done once this first step is finished.
- I think 'content types' should be a menu item in the navigation menu, not a local task. This will let us put a 'add content type' tab in the logical place when/if it is time to do that. Also this page is buried now.
- I think that the submission guidelines and minimum words should go on these pages.
- I think form_group() should be used once the form grows. We could stick what we have now in a 'Workflow' fieldset.
- I think that the 'settings' $op of hook_nodeapi() should be rethought and maybe put in another hook.
- I think that node create/edit permissions could go on these pages.
- I think that this form should have a 'save' $op and use system_settings_save() because that limits what modules can do to using variables.
- I think that there should be a 'validate' $op so modules can do validation.
- I think that the five options should be rethought.

However, these are all separate issues which should have their own patches and debate and many will have to wait until 4.7. But this gets the door open for modules and ideas in 4.6.

I'm willing to put more in the overview table, but I would like input on what it should look like to avoid width problems and be as usable as possible moving forward. Perhaps that should wait for another patch?

BTW, I consider the added 'else' in system.module to be a bugfix. I'm not exactly sure why system_settings_save() does a drupal_goto(), but it helps make the form act a lot more predictably if it does the same type of returning or goto for whichever button is pressed.

Please file a new issue for update #16.