Seems like incorrect break for chained property and method calls

[kazrac]

In https://playground.csharpier.com/ I have played around with chains and following does not seem right:
Input:

someLongNameField
    .Method0()
    .Property0
    .Property1
    .Property2
    .Method1()
    .Property3
    .Array1[1]
    .Property4
    .Property5
    .Method2()
    .Method3("some input")
    .Method2()
    .Property6
    .Property7
    .Array2[2]
    .Property8
    .Method4("some input")
    .Property9
    .Property10;

output:

someLongNameField.Method0().Property0.Property1.Property2.Method1().Property3.Array1[
    1
].Property4.Property5
    .Method2()
    .Method3("some input")
    .Method2()
    .Property6.Property7.Array2[2].Property8
    .Method4("some input")
    .Property9.Property10;

property and method chains are broken differently.

Other example:
input

			return _someResolver
				.Resolve(
					(
						raw
							.Settings
							.AttributeTemplate
							.Settings
							.OutputSettings[raw.TestFramework]
							.AttributeTemplate
							.Settings
							.AttributeTemplate
							.Settings
							.OutputSettings[raw.TestFramework]
							.AttributeTemplate,
						new
						{
							ClassName = className,
							TestClassName = raw.MethodSymbol.ContainingType.Name,
							TestName = raw.MethodSymbol.Name
						})
				);

output:

return _someResolver.Resolve(
    (
        raw.Settings.AttributeTemplate.Settings.OutputSettings[raw.TestFramework]
            .AttributeTemplate
            .Settings
            .AttributeTemplate
            .Settings
            .OutputSettings[raw.TestFramework].AttributeTemplate,
        new
        {
            ClassName = className,
            TestClassName = raw.MethodSymbol.ContainingType.Name,
            TestName = raw.MethodSymbol.Name
        }
    )
);

[belav]

The breaking of long chains uses the same logic as prettier, although it looks like there is a bug with the 1st case. Prettier does this with it. There is definitely a bug with the current way csharpier breaks it.

someLongNameField
  .Method0()
  .Property0.Property1.Property2.Method1()
  .Property3.Array1[1].Property4.Property5.Method2()
  .Method3("some input")
  .Method2()
  .Property6.Property7.Array2[2].Property8.Method4("some input").Property9
  .Property10;

The 2nd case ends up like this in prettier

_someResolver.Resolve(
  (raw.Settings.AttributeTemplate.Settings.OutputSettings[raw.TestFramework]
    .AttributeTemplate.Settings.AttributeTemplate.Settings.OutputSettings[
    raw.TestFramework
  ].AttributeTemplate,
  {
    ClassName: className,
    TestClassName: raw.MethodSymbol.ContainingType.Name,
    TestName: raw.MethodSymbol.Name,
  }),
);

If I remember correctly, the logic tries to group property accessors onto a single line if they fit. It seems worth exploring breaking them instead. At the very least fixing the first case, which seems to be a bug.

#451 may be related.