Changes

Updates to N&N for CDT 11.1 release

Part of #202

Consider variable templates while determining size of parameter pack

Fix type of value-dependent fold expression evaluation

Allow expansion with typeids in fold expression

Improved getting resources from the gcc commandline.

The old method assumed all resources were at the end of the line,
optionally followed by option -o.
Now the complete line is scanned for valid resource file extensions.

Defer resolving function set if target is deferred class or constructor

Fix assertion evaluating binary shifts of comparison op results

Currently CDT evaluates result type of comparison ops to the converted type of
their operands. When floating point values are compared and then the result is
binary shifted this trips an assertion trying to promote floating point value.

Fix this by limiting operand types of binary shifts to integral or unscoped
enumerations. Additionally fix return type of comparison op to be boolean value.

Resolve typedef before checking if type is unsigned

Allow const-qualified arg for __atomic builtins which accept that

Handle invalid empty c++17 fold expression early

One of Qt sample snippets contain (...) as placeholder for actual user code.
Parsing that leads to invalid class cast because buildExpression would return
fold expression token marker and not a proper ICPPASTexpression.

Fix that by handling this error early as invalid fold expression.

Restore counting iterations in computeContainsDeclaration cycle detector

A follow-up change to bug 509898 missed actually incrementing the counter,
restore it now.

Fixes: 5462bac381 ("Bug 509898 - IndexFileSet.containsDeclaration is slow and is causing UI freezes")

Return IntegralValue.UNKNOWN if recursed creating CompositeValue

Currently CDT would return empty CompositeValue if recursion creating for class
type is detected. If this happens inside CompositeValue.computeForFunctionCall()
and class type has fields, this leads to an attempt to assign a value to
non-existent index into empty values array.

Fix this by returning usual IntegralValue.UNKNOWN and additionally checking
whether created value is actually a CompositeValue instance.

Changed the template application to Hello World.

This provides a more useful template when making a simple Makefile
project.

Pulled out of #314

Correct year of 11.2 expected release

Fixes https://github.com/eclipse-cdt/cdt/commit/21e923ada7b0bc2db249f7d83962637b5ff85cd6#r104842615

Issue #167 - Core Build Makefile project build output folder.

* Issue Issue #167 was partly solved by PR #192 (commit 7911ac8a2b0).
  This change fixes the problem that after closing and opening a
  Makefile project the wrong build output location was used for the
  default Run configuration.
  The cause was that StandardBuildConfiguration.buildContainer was
  null after opening the project.

Fixes #167

Binary not found in Core Build Makefile project

Fixed the problem for Core Build Makefile projects that the output
binary could not be found during launching when the user set the
Build Output Location to "Build in project directory".
The project was only looking for binaries in the "build" folder.

Handle null "DisplayName" in registry

Fixes #330

CDT 11.1.1 Release Notes updates

Part of #332

Run Workflows on all branches and PRs

Add CDT 11.1.1 to p2 composite

Part of #332