It's used in the logging scenarios.

This change will cause our bootstrap build to fail if a threshold of server connection failures
occur.  The threshold is chosen a bit arbitrarily as valid failures can occur.  But 15 seems like
a number to warrant an investigation.  If this produces too many false positives it will be
adjusted appropriately.

Local functions have already implemented their own frame management,
including frame pointer "capturing" (which is implemented by passing a
list of frames to the local function by-ref, rather than traditional
lambda capturing which is implemented by keeping a linked list of frame
pointers to parent frames).

PR #14736 wired up local function lowering to the lambda frame pointer
machinery, which is necessary for when a local function is captured by a
lambda or converted to a delegate, but in the process it diverted
control flow for pure local function capturing to the frame pointer
machinery, which can't handle the structure of local function struct
frame pointers.

This PR resolves the issue by restoring the control flow for local
functions capturing other local functions with by-ref struct frames.

Fixes #15599

1. filter out projects that is not supported in remote host when calculating checksum
2. wrong validation on contract

unit test added

Fixes #15223.

Fixes #12940
Fixes #14110
Fixes #15640

Our current setup for .Net Core requires us to do manual assembly redirection in our MSBuild Task.  The setup has no
good way to detect at compile time when our source code and NuGet references get out of date.  This change allows us
to at least detect at bootstrap time.