[codingstd] removing exceptions for SVN Id tags

Subversion is no longer used in this project and thus the exceptions for the
svn Id: tag within the test code can be removed.
Merge pull request #1057 from paultcochrane/ptc/remove_svn_id

[codingstd] removing exceptions for SVN Id tags
ChangeLog: add GH #1061 warning (-O1 fails in nqp)
[imcc] fix GH #1061, nqp -O2: set_addr label marks a basic_block

set_addr label does mark a basic_block, dead_code_remove() needs the
label. disable old premature optimization

Fixes nqp/#160
All nqp tests pass now with parrot -O2.
[codingstd] checking C headers for line length violations
[include] wrapping lines to within 100 characters

This matches the coding standards for other C-language files.  The tests
also pass after these changes.
[io] wrapping lines to within 100 characters
[include] wrapping lines to 100 characters

This change is specific for PPC and thus I could not test it (Linux x86_64).
The change is trivial and *should* work, however it would be preferable for
someone with a PPC architecture to check that everything still works.  This
is the reason that this commit is separate to the others.

rurban: tested ok on PPC
[codingstd] fix c_parens.t 1 for thr_pthread.h and gc_api.h

while(0) => while (0)
[config] warnings for missing declarations or prototypes now errors

Parrot builds successfully with these warnings elevated to errors.
[config] Correcting debug message text in warnings.pm

What looks like a copy-paste error meant that a debug message from
`config/auto/warnings.pm` was mentioning attributes instead of warnings.
This change corrects this issue.
[docs] mentioning the `--cage` configure option for more warnings
[docs] adding notes to cage cleaners guide about FORTIFY_SOURCE

This should address the issue GH #711.
[lib] using Pod::Checker to check pod

Pod::Simple was missing many warnings and errors and thus has been replaced
by Pod::Checker.  This is sensible, since the advice given by the
`pod_syntax.t` test when errors occur is that one should use `podchecker` to
investigate errors in detail, thus we should be using Pod::Checker
internally to begin with.
[tools] fixing errors in pod found by podchecker
[t] correcting pod errors found by podchecker
[string/encoding] Adding missing =back pod statements

This fixes pod errors found by podchecker
[pmc] correcting pod errors found by podchecker
[runcore] correcting pod errors found by podchecker
[platform] correcting pod errors found by podchecker