Fix php-syntax-propertize-extend-region to extend END as well.

Previously, the function would only extend the START of the region. If
the END of the region falls within a HEREDOC, syntax highlighting
might be incorrect.

Signed-off-by: Eric James Michael Ritz <ejmr@plutono.com>
Tweak PSR-2 style by adding (substatement-open . 0)

PSR-2 states:

  Opening braces for control structures MUST go on the same line, and
  closing braces MUST go on the next line after the body.

However, in the event that the brace does go on the same line, do not
indent it.

Signed-off-by: Eric James Michael Ritz <ejmr@plutono.com>
Bump patch number for recent syntax/indentation improvements
Do not override variable tab-width when indenting with spaces.

The number of spaces to indent is controlled by the correctly set
variable c-offset-width. The value of tab-width does not influence
this. When indent-tabs-mode is nil, indentation is always acheived
using spaces, not tabs. The various modes set this correctly. However,
the modes that indent using spaces also override tab-width which might
undo a user's set value.

As an example, a user may prefer a literal tab (not code indentation)
be rendered as 8 spaces. And so this user would set tab-width to 8 in
init.el. All PHP modes override this value even when not using tabs
for indentation. This mean's the user's preferred tab width is altered
for no gain.

I prefer using tab-width 8 so I can quickly see when code is
incorrectly indented with tabs instead of spaces. The overriding of
this value breaks this for me. Of course, I workaround this by
re-setting tab-width in hooks, but why put the user through this in
the first place.

Coding styles that indent using tab (such as wordpress) remain
unaltered.

Signed-off-by: Eric James Michael Ritz <ejmr@plutono.com>