Better handling of Java interfaces

Handle Java interfaces without relying on untracked newlines so that
nl_remove_extra_newlines can be nonzero. Also handle the keyword
@interface during tokenization so that it is not mishandled. Tests
80011-80014 are added as well.
Explicitly recognize '@interface' as class-like keyword

In Java, treat '@interface' like the keyword 'class', including all
implied indentation. This changes the results of 80010, and as such is
a distinct commit.
Fix applying sp_before_dc rule with decltype

Rule wasn't applied and one space was forcely added in the following example:
std::vector<uint8_t> v;
decltype(v)::const_iterator it;
Merge pull request #196 from villytiger/decltype

Fix applying sp_before_dc rule with decltype
Merge branch 'master' of https://github.com/npnth/uncrustify into npnth-master
Remove unused local variable.
Use tok_ctx.expect() in a few more places.
Treat class names with array indicators as CT_TYPE in Java

Extends the 'word followed by word is type' check to skip past
intermediary (nested and stacked) sets of bracket.
Simplify chunk_get_next_nisq
Fix crash due to incorrect NULL check.
Split the constructor initializer use CLASS_COLON into CONSTR_COLON.

Keep all the options the same, so there is no change in test output.
Add options sp_after_constr_colon and sp_before_constr_colon

Assuming that indent_ctor_init_leading was only meant to apply to the
constructor colon, not the class declaration.
No tests fail, but that may be because there is no test coverage.
New options: indent_constr_colon, nl_constr_colon, nl_constr_init_args,
pos_constr_comma, pos_constr_colon

This should finish the split between the class initializer list and base
class list.
Update config files for the CLASS_COLON/CONSTR_COLON split
Mark stuff between a class base ':' and the '{' as IN_CLASS_BASE
There cannot be variables to align in a class base list
Add another class colon test
Update the README file to indicate that bugs should go on the sf.net site

That info is also in the BUGS file, but github.com doesn't show that.
Less fragile array-as-type handling

Handle [], [N]-skipping in a better section of the code, which fixes
some restrictions on the number of type tokens before an array for
recognition (i.e. `final int[] a;' would be recognized, but `int a[];'
would not). Test 80030 is updated to reflect this.
Fixed invalid Objective-C array literal syntax in tests. Arrays use square brackets, not braces.