Concordion.NET appears to have FullOGNL switched on by default

[nigelcharman]

The Java implementation of Concordion restricts the expression language to a sensible subset of expressions, so that specifications are kept simple and maintainable. If users really want to work around this, the annotation FullOGNL enables [complex expressions].

In Concordion.NET, the complex expressions appear to be enabled by default. For example, changing the fixture in the tutorial to return an array:

    public string[] Split(string fullName)
    {
        Result result = new Result();
        return fullName.Split(' ');
    }

and the spec to use array expressions:

        into first name <span concordion:assert-equals="#result[0]">Jane</span>
        and last name <span concordion:assert-equals="#result[1]">Smith</span>.

does not cause an error.

We should update Concordion.NET to be consistent with Concordion.