Issue #14937: Migrated section 3.4.2.1 Overloads: Never Split to follow Chapter Wise Testing approach

[Zopsss]

issue #14937

migrated the section and added some new test cases in records input file

[romani]

Is it possible to have at least one Input that have no violations ? like: InputCorrectOverloadsNeverSplit

all other Inputs can have violations and any name we like
we will use such Inputs to run google formatter to make sure we are not conflicting with it, files will be selected by pattern **/it/**/InputCorrect*

item:

[Zopsss]

CI is failing but it does not affect the PR

https://dev.azure.com/romanivanovjr/romanivanovjr/_build/results?buildId=21783&view=logs&j=d72e04f6-d294-5bfe-b3cd-ffcb523f40f9

[Zopsss]

Is it possible to have at least one Input that have no violations ? like: InputCorrectOverloadsNeverSplit

all other Inputs can have violations and any name we like we will use such Inputs to run google formatter to make sure we are not conflicting with it, files will be selected by pattern **/it/**/InputCorrect*

I think we should do this when we're using verifyWithWholeGoogleConfig() because then we will be following all the rules of google style.

With the current method we're only following some specific rules. If we run google formatter against these inputs then it will format all the bad code and it will be hard to find if we're following the style guide properly or not.

[romani]

Sounds good. We will do this as separate phase of updates.

[romani]

Ok to merge

[romani]

@rdiachenko , canceled jobs can be ignored for this PR.

[rdiachenko]

@Zopsss please fix conflicts

[Zopsss]

Reverted all section names I modified in previous PRs to their original names. I added support to properly validate section names here: #15030 (comment). I forgot to revert section names in that PR so I did it here

[Zopsss]

@rdiachenko conflicts resolved

[rdiachenko]

lgtm