Update interactive console document
Make some minor performance & UI changes to AutoConfigMaker.

-Provide more information in error dialogs on failed configure attemtps.
-Make some minor performance tweaks.
Make e4 bundles optional.

Fixes PyDev on Eclipse 3.7
Improve interpreter configuration error reporting.

-Ignore interpreters missing standard libraries for Quick Auto-Config,
but still permit them for Advanced Auto-Config.
-Revise errors that are reported on interpreter config failure.
-Localize some "error tracking" variables in AutoConfigMaker.
Remove "null result" error case for when configuring an interpreter.

Remove a bug that reports an error if the folder selection dialog for
an interpreter being configured is closed.
Whitespace only changes
Change Limit before skipping calculation of min/max
Use Tuple3 instead of 1 length arrays to return multiple values
Use a multi-status to display error message
Minor optimization: only expand outline to level 2 initially and disable redrawing on expand all/collapse all operations.
Merge pull request #100 from jonahkichwacoders/fix_for_3.7

Make e4 bundles optional.
Merge pull request #101 from jonahkichwacoders/change_limit

Change Limit before skipping calculation of min/max
Merge pull request #97 from jonahkichwacoders/bug_230_interactive_console_docs

Update interactive console document
Respect pydev_interpreter_new_custom_entries extension point

It used to be (prior to the new auto-config changes, 9a423ec) that askUserInOutPath was the method for telling if frpmString was being
called from a user configuring a new interpreter or by restoring a previously stored one.

A previous fix in 67cef68 addressed one place where the meaning of
the variable changed. This fix extends that fix to add additional
interpreter settings with Quick-Config is used and hence askUserInOutPath
is false.
Fixed comments.
Minor
Fixed issue on interpreter synchronization where we could start multiple check processes when it stopped to ask information to the user (in a dialog).
Fixed issue where the debugger would not work if the user had unicode characters in the path for a file which had breakpoints -- mainly, all that's decoded from java is now expected to be in utf-8 and unicode is used internally and encoded as needed (which is something we actually did already for python 3).
Merge pull request #1 from jonahkichwacoders/andrew-pr-93

Some suggestions for pr-93 branch
Bug fixes and UI touch-ups to interpreter config.

-Fix critical bug in AutoConfigMaker#autoConfigSingleApply.
-Adjust the way errors are displayed for auto-config failures.
-Display the name of the failed interpreter in error dialogs/messages
for all configuration failure cases.
-In AutoConfigMaker, use a new shell every time a shell is needed
rather than the same one all the time, to prevent possible problems
that might occur if the dialog a background config operation was
started in is closed.