Suppress one in code generated by flex.

The last KDevelop3 release was many years ago, in 2008 I think.
I haven't seen or read about anybody using KDevelop 3 since a
long time, so I think it can safely be removed from CMake.
KDevelop 4 (first released in 2010) has its own proper CMake
support now, independent from this generator.

Alex

If warnings appear we want to match and/or suppress them independently.
Always suppress the warning summary.

The `WarningMessagesDialog.cxx` source file name is displayed by
MSVC in the compiler output, and the CTest launcher matches the
name as a warning line starting in "Warning".  Suppress this
false positive with a custom exception.

Revise the manual procedure in the `*Lexer.in.l` files.  Some of our
post-processing steps are no longer necessary with the current set of
supported compilers.  Some steps changed with newer versions of flex.

Then regenerate all lexers with flex version 2.6.1.

All clients of `cm_sha2` have been ported to `cmCryptoHash`, which now
uses librhash internally.

We will match/ignore the actual warning lines, if any, so we can always
ignore the summary line if present.

Clang scan-build warns in some expansions of RB_GENERATE_STATIC
that it has a "Dereference of null pointer".  It also warns that
"The left operand of '==' is a garbage value" strangely.  Simply
suppress these since this is third-party code anyway.

The Clang scanbuild tool warns:

    Utilities/cmliblzma/liblzma/simple/x86.c:106:23: warning:
    The result of the '<<' expression is undefined
      src = dest ^ ((1u << (32 - i * 8)) - 1);
                     ~~~^~~~~~~~~~~~~~~

AFAIK overflow of a left shift on an unsigned type is well-defined.

We first suppressed this in commit v3.1.0-rc1~647^2 (CTestCustom:
Suppress warnings about rand() and srand() on OpenBSD, 2014-04-12).
Add another variant of the warning wording.

Our `cmake.version.manifest` file uses a "compatibility" element for
Windows 10 support.  Older MS tools warn about it being unknown, so
suppress the warning.

On Solaris the system `/usr/include/floatingpoint.h` header contains

 typedef float single;

so the GNU compiler warns that uses of the name `single` shadow it.
Just suppress the warning because our uses of this name would become
less readable with a different name.

KWIML no longer uses a configured prefix.

Extract upstream KWSys using the following shell commands.

$ git archive --prefix=upstream-kwsys/ dc4e4a55 | tar x
$ git shortlog --no-merges --abbrev=8 --format='%h %s' cfeb27cc..dc4e4a55
Ben Boeckel (1):
      dd466688 CTestCustom: use list(APPEND)

Domen Vrankar (1):
      dc4e4a55 SystemTools: Handle directories in CopyFile{Always,IfDifferent}

Add the PackageCertificateThumbprint property when there is a
certificate on a WindowsStore or Phone app.

The test covers exceptional behavior that leaks memory, so ignore it for
dynamic analysis runs.

Extract upstream KWSys using the following shell commands.

$ git archive --prefix=upstream-kwsys/ f63febb7 | tar x
$ git shortlog --no-merges --abbrev=8 --format='%h %s' c9336bcf..f63febb7
Brad King (1):
      83b4a6b8 Process: Fix conversion warning in testProcess.c

James Johnston (7):
      4cd8846c Process: Remove trailing whitespace in ProcessUNIX.c
      b1c44c58 Process: Refactor sleeping code in testProcess.c.
      faff2ab0 Process: Wait for children to terminate on Ctrl+C.
      ef517b19 Process: Added initial support for process groups.
      906c2cae Process: Added test cases for testing Ctrl+C and process groups.
      52874e6a Process: Fix leaked file descriptor in ProcessUNIX
      f63febb7 Process: Fix error message for startup failure on Windows

The HP compiler on HP-UX 11.11 warns:

 Warning (anachronism) 823: ".../test_INT_format.h", line 194 # Redundant
 preprocessing concatenation operation results in two valid preprocessing
 tokens. Depending on this implementation defined behavior will result in
 non-portable code.
       TEST_C(INT32_C, -0x55000000, i32, int32_t, uint32_t)
       ^^^^^^
 Warning (anachronism) 823: ".../test_INT_format.h", line 196 # Redundant
 preprocessing concatenation operation results in two valid preprocessing
 tokens. Depending on this implementation defined behavior will result in
 non-portable code.
       TEST_C(INT64_C, -0x5500000000000000, i64, int64_t, uint64_t)
       ^^^^^^

There is likely a subtle problem with the way one of the system-provided type
macros is defined but the test passes despite the warning.  Simply suppress it.

We don't do crypto here, so a "poor" random doesn't matter. In fact we have API
to allow people to get a repeatable sequence by setting a specific seed.

This is third party code and we know that at run time the correct
alignment is achieved.

We already do so for QtCore and QtGui headers.

Clang -Wunreachable-code-return warns on some generated lexer code.

Such notes only appear with other diagnostics and should not be
considered a warning on their own.

Since we compile command implementations in large batches the
translation units get too big for MIPSpro optimization limits.
Suppress the warnings it produces:

 Warning: Olimit was exceeded on function ...
 Warning: To override Olimit for all functions in file, use -OPT:Olimit=3201

Add a warning suppression regex to match:

 LINK : warning LNK4089: all references to 'SHELL32.DLL' discarded by /OPT:REF

Add a warning suppression regex to match:

 LINK : warning LNK4089: all references to 'PSAPI.DLL' discarded by /OPT:REF