* Correctly handle default and params arguments in cfg for pattern based disposal

Allow pattern matching `null` against pointer types when the pointer types contain nested type parameters (#49915)

The pattern matching codepath for types involving type parameters was not excluding pointer types from being considered value types, and was marking things like `((T*)null) is null` as not being allowed.

* Handle types that contain ref-like types in value returns.

* Add positive test case
Co-authored-by: NJared Parsons <jaredpparsons@gmail.com>

* Add additional assert that a compound assignment on a function pointer has a ref-returning signature if it got to local rewriting.

Added support to normalize accessor list for a property/indexer/event on a single line when there are no accessors with block body. (#49495)

The discussion started here: https://github.com/dotnet/roslyn/issues/49468

The work consisted in:
- Added support in the SyntaxNormalizer class for the auto-properties (the ones who have null Body property)
- Added more tests for properties including init accessor and initializers
- Fixed the two existing tests (property and indexer) to reflect the changes

The following comparisons shows the results of the actual tests, before and after this PR.

```
Before:
class a
{
  b c
  {
    get;
  }
}

After:
class a
{
  b c { get; }
}

```

```
Before:
class a
{
  int X
  {
    get;
    set;
  }

  = 2;
}

After:
class a
{
  int X { get; set; } = 2;
}
```

```
Before:
class a
{
  int Y
  {
    get;
    set;
  }

  = 99;
}

After:
class a
{
  int Y { get; set; } = 99;
}
```

```
Before:
class a
{
  int Z
  {
    get;
  }
}

After:
class a
{
  int Z { get; }
}

```

```
Before:
class a
{
  int T
  {
    get;
    init;
  }

  int R
  {
    get => 1;
  }
}

After:
class a
{
  int T { get; init; }

  int R { get => 1; }
}

```

```
Before:
class a
{
  int Q
  {
    get
    {
      return 0;
    }

    init
    {
    }
  }

  int R
  {
    get => 1;
  }
}

After:
class a
{
  int Q
  {
    get
    {
      return 0;
    }

    init
    {
    }
  }

  int R { get => 1; }
}

```

```
Before:
class a
{
  int R
  {
    get => 1;
  }
}

After:
class a
{
  int R { get => 1; }
}
```

```
Before:
class a
{
  int S => 2;
}

After:
class a
{
  int S => 2;
}
```

```
Before:
class a
{
  b this[c d]
  {
    get;
  }
}

After:
class a
{
  b this[c d] { get; }
}


```

Ensure that each generic local function gets its own container to cache dynamic call-sites. (#49802)

Fixes #49599.

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1243877.

Fixes #49754.

Refactor the signature of LogDiagnostic as LogDiagnostic(Diagnostic diagnostic, SuppressionInfo? suppressionInfo).

* Avoid sharing NullableWalker state between method and nested functions

* PR feedback

* Check _localFuncVarUsages

* Misc.

* Code cleanup

* Handle try/finally blocks

* Check for specific BoundNodes

* PR feedback

* Remove parameter

Report an error for an initialization of a ref-returning property as part of an object initializer inside an expression tree. (#49719)

Fixes #49617.

- In product code, when the access part yields non-nullable value, use coalesce expression instead.
- In VB lowering, use coalesce expression instead of synthesized Nullable.GetValueOrDefault call under the same conditions when result is also Boolean.

Related to #38306.

AddSynthesizedRecordMembersIfNecessary - avoid touching members that are known to have no effect on the outcome of the function. (#49610)

This avoids unnecessary work and fixes #49286.

Address feedback to ensure `/warnaserror-:ID` prevents config options from bumping a warning to an error.

Verified that the new test fails for the case `[InlineData(warnAsErrorMinus: true, defaultSeverity: DiagnosticSeverity.Warning, severityInConfigFile: DiagnosticSeverity.Error, expectedEffectiveSeverity: DiagnosticSeverity.Warning)]` prior to the product fix in this commit, as actual effective severity was an error. This is fixed with commit.

Fixes #49341.

* Encapsulate OperationMapBuilder implementation and expose a single helper method instead of the entire visitor. Additionally cleaned up the implementation to be more idiomatic.
* Tightened assertions in the Operation base class and removed uneeded code.
* Clarified comments and assertions around the TemporaryBlock scenario.