New Policy: ProhibitAugmentedAssignmentInDeclaration

This was created from a patch provided by Mike O'Regan.
See http://perlcritic.tigris.org/ds/viewMessage.do?dsForumId=4230&dsMessageId=2735595
Since we imported the firstval function, we might as well use the imported symbol.
Fix self-compliance problems in new Policy.
Turn on svn:keywords
Bumped version number
Prepare change log for release.
Add OpenSUSE to links page.
Fix typo (thanks, petdance)
RT #74647: False positive in TestingAndDebugging::ProhibitNoWarnings
(bad parsing)

The problem here was that the original code just stringified the
'no' statement, used a regular expression to extract all lowercase
strings, and then grep'ed out 'no', 'warnings', and 'qw'. Unfortunately,
'qw' is an actual warning category (believe it or not!), so the original
code saw

 no warnings 'qw';

as an unqualified 'no warnings'.

The patch recurses into the statement being analyzed, and finds all:
* PPI::Token::Word (because of 'foo => "bar"'),
* PPI::Token::Quote (because of "'foo'"), and
* PPI::Token::QuoteLike::Words (obviously).
The first two words (which are 'no' and 'warnings') are discarded, and
the rest are subjected to analysis. Note that, though the original code
rejects everything that is not entirely lower case alphabetic, the patch
accepts everything. My reason is that the difference was a "don't care",
becaue unknown warning categories don't compile, and thus are not
Perl::Critic's problem.
MANIFEST is now stashed in the repository.

Even though it is a generated file,  M::B and EU::MM
both expect it to be there before making a build.  We
believe one should be able to checkout from the repository
and run the usual build/test/install cycle without
any surprises.

This resolves RT #43908.
RT #74429: 'Negative array index should be used' a little misleading

The problem was that the documentation of
Variables::RequireNegativeIndices did not mention at all the fact
the semantics of $#foo-$n change when $n becomes greater than $#foo,
whereas the semantics of -$n do not. The author of the ticket seems to
have been burned when trying to straighten out non-compliances.

The long explanation of a non-compliance has been revised to feature the
semantics change prominently.

The short explanation has not been changed, because I confess my
inability to do significantly better without taking significantly more
verbage.
RT #75397: ProhibitBuiltinHomonyms should include the sub name in the
error message

I took a swing at this. Just a matter of adding $elem->name() on the end
of the message.
RT #77510: Left curlys as literals in regexps are deprecated.

The use of left curly brackets ("{") as literals in regular expressions
is deprecated, and as of Perl 5.17.0 produces a compiler warning. Given
the code policies required for self-compliance, the solution is to make
them into a singleton character class (i.e. "[{]").

A change in the version of PPIx::Regexp was also done, because that also
turned out to have literal curlies (blush!).
perlcritic-gui now ships with ActivePerl, not PDK.

Thanks to Thomas J. Dillman for letting me know.
Add ActivePerl to the stop words list.
RT #77977: Perl::Tidy 20120619 breaks CodeLayout::RequireTidyCode

Perl::Tidy version 20120619 breaks CodeLayout::RequireTidyCode. There
appear actually to be three breakages:

1) The stderr argument to perltidy() no longer takes a scalar reference.
This is a documented change. Fortunately Perl::Critic already has
IO::String as a dependency, so the solution is to instantiate an
IO::String object from the $stderr variable, and pass that.

2) Perl::Tidy now chomps the perltidyrc string.  This fails if it is
passed a reference to a Readonly::Scalar, and throws an exception. The
solution is to assign $EMPTY to a scalar variable, and pass that.

3) If you pass a scalar reference as the source argument to perltidy(),
it is modified after the call -- the trailing newline is removed. The
only solution I can come up with is more ad-hocery.
Bump version number
Note VERSION and release date in change log.
RT #77977 requires us to upgrade to Perl::Tidy version 20120619.
Actually, it seems like we don't need the newer Perl::Tidy.
It still works with older versions.