Cabal V3.0 changes how "freeform" fields are parsed

**Describe the bug**
Since Cabal V3.0, `freeTextField` `freeTextFieldDef`, `freeTextFieldDefST` uses the function `fieldlinesToFreeText3`. Prior to Cabal V3.0, we use `fieldlinesToFreeText`. However, `fieldlinesToFreeText` treats lines with only dots (let's call them dotlines) as empty lines and `fieldlinesToFreeText3` doesn't.

**To Reproduce**
Steps to reproduce the behavior:

- Look at cabal on hackage
-

This dot is a dotline that used to be interpreted as a empty newline.

**Expected behavior**
Is this a breaking change in the cabal parser since cabal3.0?

Start by comparing the mentioned fieldlinesToFreeText and fieldlinesToFreeText3 functions, then reproduce the dotline behavior using the Cabal package example on Hackage. Done means the parser's intended treatment of lines containing only dots is established and the Cabal 3.0 behavior is corrected or explicitly confirmed.

Written by the indexing model from the issue text.