The problem here was when we do cycle detection, we tried to look
at the source of the candidate constructor that we are looking at
delegating to. If we are in a cross-language case, the target might
be from metadata via the skeleton reference and we don't have source.
Rather than fixing the code that assumes it's a source method, I'm
making a change that says if the constructor you're delegating to is
in the base type, then we can't create a cycle and can skip the check
entirely.

We tried to locate a constructor to delegate to; in that case we would
grab the types of the constructor and make sure the original call site
actually can use those types. In the cross-language case, we'd mix up
types from different languages. The correct behavior here is to map
the candiate type back to the language of the call site, since it's
the call site's language rules that matter.

Fixes https://github.com/dotnet/roslyn/issues/49850

```
# IDE0060: Remove unused parameter
dotnet_diagnostic.IDE0060.severity = warning
```

Remove naming styles before generating field/property/parameter in constructor related refactorings (#36220)

* Fix for 35776

* helper struct implemented

* Respond to feedback

* Tests in progress

* Add tests

* fix tests

* fix tests

* Respond to feedback

* Handle empty base names

* Add test for recursive removal of prefixes, and other minor feedback responses

* Fix tests

* Fixes 14077

* Respond to feedback

* More tests

* Add FallbackNamingRule for parameters

* Fix default parameter naming rule

* Use parameter naming style, add tests

* Rename Foo to Goo

* Rename ifoo to igoo

* Add back BOMs

Apply feedback from Pilchie
Apply feedback from CyrusNajmabadi
Missed feedback from CyrusNajmabadi
Apply more feedback from CyrusNajmabadi and AlekseyTs
Apply feedback from AlekseyTs
Apply feedback from jcouv

These tests were all using WpfFact, but not actually doing anything
that required either WPF or an STA thread. We plan to enable
parallelization of Facts (but not WpfFacts), and this ensures we can
parallelize as many tests as possible.