Allow more undentation for tuples and dot-access (or give indentation warning instead of error)

**I propose we** fix these two inconsistencies with indentation
```fs
let r = (task {
(),
(), // go left as much as you want, can't go right
()
}) // go right as much as you want, can't go left more than opening ( IF we have .Result below. remove .Result below and it is OK again
.Result
```

**The existing way of approaching this problem in F# is** experiment with indentation until errors go away.

## Pros and Cons

**The advantage of making this adjustment to F# is** less unexpected errors with indentation

**The disadvantage of making this adjustment to F# is** implementation complexity in the compiler.

## Extra information

**Estimated cost (XS, S, M, L, XL, XXL):** M

**Related suggestions:** https://github.com/fsharp/fslang-suggestions/issues?q=indent

## Affidavit (please submit!)

Please tick these items by placing a cross in the box:
* [x] This is not a question (e.g. like one you might ask on [StackOverflow](http://stackoverflow.com)) and I have searched StackOverflow for discussions of this issue
* [x] This is a language change and not purely a tooling change (e.g. compiler bug, editor support, warning/error messages, new warning, non-breaking optimisation) belonging to [the compiler and tooling repository](https://github.com/dotnet/fsharp)
* [x] This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it
* [x] I have [searched both open and closed suggestions on this site](http://github.com/fsharp/fslang-suggestions/issues) and believe this is not a duplicate

Please tick all that apply:
* [x] This is not a breaking change to the F# language design
* [x] I or my company would be willing to help implement and/or test this

## For Readers

If you would like to see this issue implemented, please click the :+1: emoji on this issue. These counts are used to generally order the suggestions by engagement.

Start with the tuple and dot-access indentation example, then review the related indentation suggestions linked in the issue. Clarify whether the desired outcome is more permissive indentation or a warning instead of an error; done requires an agreed language-design direction and corresponding compiler implementation and tests.

Written by the indexing model from the issue text.