This commit is a complete rewrite of the core mustache.js file with two
main goals: 1) a major performance boost and 2) better compliance with
the mustache spec.

In order to improve performance templates are pre-compiled to JavaScript
functions. These compiled functions take a view, a partials object, and
an optional callback as arguments. They are cached to prevent
unnecessary re-compilation of an already compiled template. Both of
these enhancements facilitate a generous boost in performance.

A few other notes:

- The mustache.js file is now both browser and CommonJS ready without
  any modification.
- The API exposes two main methods: Mustache.compile and
  Mustache.render. The former is used to generate a function for a given
  template, while the latter is a higher-level function that is used to
  compile and render a template in one shot. Mustache.to_html is still
  available for backwards compatibility.
- The concept of pragmas is removed to conform more closely to the
  original mustache spec. The dot symbol still works to reference the
  current item in an array.
- The parser is much more strict about whitespace than it was before. The
  rule is simple: if a line contains only a non-variable tag (i.e. not
  {{tag}} or {{{tag}}}) and whitespace, that line is ignored in the
  output. Users may use the "space" option when compiling templates to
  preserve every whitespace character in the original template.
- The parser is able to provide detailed information about where errors
  occur when parsing and rendering templates, including the line number
  and surrounding code context.

It was confusing to present the concept of dereferencing a nested object and
enumerating over a list in an same example intended to show dereferencing a
nested object. I believe this example illustrates the concept more clearly.

I was getting the following error when running `rake commonjs`:

```
rake aborted!
no such file to load -- rspec/core/rake_task

(See full trace by running task with --trace)
```

This was with a default OS X Lion install. The issue was simply that
rspec was not installed, however, it may not be obvious at first.

If a section key returns a function, it will be called
and passed both the unrendered block of text and a renderer
convenience function.

Given this JS:

  "name": "Tater",
  "bolder": function() {
    return function(text, render) {
      return "<b>" + render(text) + '</b>'
    }
  }

And this template:

  {{#bolder}}Hi {{name}}.{{/bolder}}

We'll get this output:

  <b>Hi Tater.</b>

As you can see, we're pre-processing the text in the block.
This can be used to implement caching, filters (like syntax
highlighting), etc.

You can use `this.name` to access the attribute `name` from
your view.