Fix console mixed case optional value params

This one slipped through.

When using optional value params in console routes, i.e.
````
do something [<withThisData>]
````
Given the following script invocation:
````
./zf2 do something "with foo"
````

We would receive the following route match:
````php
// actual
[
  'withthisdata' => 'with foo'
]
````
Where it should be:
````php
// expected
[
  'withThisData' => 'with foo'
]
````

Notice that `withThisData` parameter became lowercased `withthisdata`.

@weierophinney - we need to include a note on that in release notes, in case someone just ignored the bug and consumed all-lowercased parameter names.