Google is deprecating version 1 of their custom search element API
sometime in April. While we don't generate actual elements using their
code, we use their javascript libraries to call the search. This
change updates the code for version 2, removing the deprecation warning
and keeping things in compliance.

Before working with this, read
https://developers.google.com/custom-search/docs/element
very carefully. The flow of the Google Search as it relates to UNL_Search
is:

1) end-scripts.tpl.php is rendered with variables that include the custom
search engine ID

2) This script, using search.js (or search.min.js), adds the google search
javascript to the end of the page asynchronously. It also gives the callback
for its loading as window.searchInit, which loads the UNLSearch.initialize
function.

3) This sets up the various search capabilities, binds callbacks onto those
actions, and has all the JS functions that we operate on in the search.

I didn't need to use the <gsce> element as described in the docs,
as we already have a text box to search, and I bind the results to
the unl_results div (local_results if a site-search is executed).

Lastly, this new code does not use the "Linked Search Engine" specification.
Instead, the as_sitesearch parameter is passed into the Google API,
or, if a specific Custom Search Engine is specified (cx parameter),
that is used vs. our regular UNL one.

Google search tool appears to be communicating with the search page via
multiple domains. Prevent that communication from triggering searches
with Google data.

Messages posted from the same domain or browser exentions will be
ignored.

When a local search occurs (not triggered by explict tab click),
automatically switch to the "All of UNL" tab if no result are detected.

The v1 API method "execute" needs an object as the third param to avoid
a TypeError.

This allows other objects (namely the Directory controller) to trigger
an interface change.

The Directory controller triggers a UI change when their are no results
for the current filtered view state.

API error.

Also remove extra eclipse junk missed in previous commits

Reverting r87 as the Google API bug has been addressed and rolled out. @see http://www.google.com/support/forum/p/customsearch/thread?tid=3a08ffc4ad03d4c7&hl=en

Added a hack that works around a bug in the google API that prevents the use of linked CSE's via the {crefUrl: ""} in the CustomSearchControl constructor. The hack uses API calls that are part of the depricated search API, but it appears to restore functionality.

Refactored the searchInit function to utilize a standard form rather than google's deprecated gSearchForm. Uses the onSearchStart callback to chain the peoplefinder and local searches. Removed unused functions.