Fix minor issue with node type names. (This technically prevents XSS with content type names, but if you're giving out the ability to create / edit content types to people you don't trust, you have much bigger problems.)

Pamela Fox says to add overflow: hidden; to fix the "long copyright strings run out the left end of the map div" bug.
http://code.google.com/p/gmaps-api-issues/issues/detail?id=308

So, by popular demand, I'm adding a CSS rule for that.

Tested in Seamonkey and IE6.

Fixing align brokenness noted in comment 66 of #266595. I was treating a string as an array and accidentally stomping some css classes.

Make a slight change to how gmap element processing works. This should reduce warnings.
Add some tests.

I have run the images through pngout to bring down the file size significantly. I also went and organized them in what I hope is a logical order. (modified light spectrum order)
Note: The old "small red" and "small blue" have been renamed to "alt small red" and "alt small blue"! If you were using these two markers in macros, and wish to keep the same look as before, please update your macros.
The new markers have thinner borders.

#310357 reported by bobchristenson: Remove code that makes map/node 404 if there weren't any results.
#310365 reported by bobchristenson: Fix "map/nodes" typo in fieldset title.

* Reduce the number of variables used by the location map block.

Since I keep making the mistake of using comma delimited behaviors in macros, we might as well support the syntax.

Did some theme function renaming for gmap_location to be more in line with the 6.x way of doing it.