Add syntax highlighting for template files

Adds highlighting for the various keywords that vim-template expands on
top of the default syntax highlighting for the template file's
respective language.
Add GetGlobalTemplateDir()

Returns the user's global template directory if it exists, otherwise
returns the default template directory
Hard-set the prefix used in the global templates directory

Because the global templates directory is dedicated solely to storing
globally available templates for vim-template, there's no real reason to
have it share the same prefix that templates in other directories use.
Sharing the same prefix means if the user ever changes the prefix from
their .vimrc, every single global template will disappear until they
rename all of them to match the new scheme. This also means updating
with plugins like pathogen or vundle will throw errors with git, which
we'd really like to avoid.
Move the syntax file autocommand to it's own section
Add syntax file autocommand for global templates
Change default prefix to something less ambiguous

The default prefix, "template." leads to a painfully ambiguous regex
that makes it pull in the wrong templates for the wrong filetypes. For
example; by default "template.m" is included in the global templates.
When we strip the prefix to check for matching template files, we get
stuck with the only search criteria being the letter "m", so we get
stuck with it pulling in files like "foo.vim" that are completely
unrelated.

The other alternative to fixing this would be setting the prefix to
something without a dot in the front so the dot gets included in the
template matching criteria. However, this means you'd have to specify
the pattern for the template right after the template's filename, which
would lead to weird and potentially misleading filenames like
"templatefoo.c", unless you were to stick solely to specifying file
extensions as patterns.

I've chosen this prefix by default because it has the following
advantages:
  - It starts with a period, so it won't clutter directory listings
	since it will be hidden by default default (which is what I think
	most people like by default)
  - The pattern you wish to match begins after a colon. Colons are rare
	in filenames, and their punctuational meaning is clear to most
	people, and it makes it a lot easier to visually separate the regex
	in the filename from the prefix.

The only downside to this is that it doesn't work in Windows systems by
default, but if you managed to get gvim installed and working properly
on a Windows system you're probably smart enough to know to look in the
documentation and change it yourself.
Change prefix for global template directory

Changed from "template." to "template"
Use the proper template prefix in <SID>TemplateBaseNameTest()
Use limited shell-style globbing for template matching

The previous method of allowing regular expression matches with
templates doesn't really fit in well. I imagine that most users by
default assume that patterns for matching a filename on any sort of *nix
affiliated software are normal shell-style globbing patterns, not
vimscript regex patterns. Plus, it makes a lot more sense for working
with filename patterns and makes template names a lot more legible.

As of now this only really supports the bare basics of shell-style
globs; '.', '?', and '*'. I can't think of any reasonable use cases
where you'd need anything more complex then those with a vim template.
I'm sure if someone wants us to add the rest of the features they can
file an issue later.
Change naming scheme for global templates

When using shell-style globbing for templates, this naming scheme makes
a lot more sense and is far more legible
Don't match anywhere in the string by default

If we don't match anywhere in the string when checking the regexes in
template names, matching extensions will have to be done with '*.foo' as
opposed to '.foo'. This makes more sense with shell-style globbing and
'template:*.foo' is a lot easier to read than 'template:.foo'.
Fix filetype detection for global templates
Update documentation
Notes in README about installation/update using Vundle

Inserts a couple of notes about Vundle working just fine for bundle-based
installs, and how to update using its :BundleUpdate command.