partial parameters are lower on the stack than context

Nobody has claimed this yet.

When giving a partial parameters, they are pushed down the stack and the previous context is pushed onto head. If there are two variables with the same name, then the partial parameter will be hidden by the higher context.

This is confusing default behaviour and seems inconsistent to how sections operate.

I'm aware of the changes introduced by #132 - but this seems like a hack to fix the issue of not searching a higher context ( #271 ).

See example below. Expect x=2, but it is x=1.

``` javascript
dust.loadSource(dust.compile("partial says x={x}", "part"));
dust.loadSource(dust.compile("{>part x=\"2\" /}", "test"));
var data = {
x :1
};

dust.render("test", data, function(err, out) {
$("body").html(out);
});
```

The supplied JavaScript reproduction uses dust.loadSource, dust.compile, and dust.render; start there and trace how partial parameters and contexts are resolved. Done means the example renders x=2 while section lookup behavior remains consistent, with coverage for both cases.

Written by the indexing model from the issue text.