Run fourmolu against plutus-tx-plugin files

[SeungheonOh]

Formatted plutus-tx-plugin files with fourmolu and stylish haskell(through pre-commit hook)

[SeungheonOh]

These test are failing:

    Coverage
      9.6
        Application heads and line coverage
          noBool
            correct application heads:             OK
            correct line coverage:                 FAIL
              test/Plugin/Coverage/Spec.hs:84:
              Lines [31] are not covered by [(30,30)]
              Use -p '/noBool.correct line coverage/' to rerun this test only.
          boolTrueFalse
            correct application heads:             OK
            correct line coverage:                 FAIL
              test/Plugin/Coverage/Spec.hs:84:
              Lines [34] are not covered by [(33,33),(33,33),(33,33),(33,33)]
              Use -p '/boolTrueFalse.correct line coverage/' to rerun this test only.
          boolOtherFunction
            correct application heads:             OK
            correct line coverage:                 FAIL
              test/Plugin/Coverage/Spec.hs:84:
              Lines [37,40,41,42] are not covered by [(36,36),(39,39),(39,41),(39,41),(40,40),(40,40),(40,40),(40,40),(41,41),(45,45),(45,45),(45,45),(45,45),(45,45),(45,45)]
              Use -p '/boolOtherFunction.correct line coverage/' to rerun this test only.
          boolQualifiedDisappears
            correct application heads:             OK
            correct line coverage:                 FAIL
              test/Plugin/Coverage/Spec.hs:84:
              Lines [49] are not covered by [(48,48),(48,48)]
              Use -p '/boolQualifiedDisappears.correct line coverage/' to rerun this test only.

[SeungheonOh]

Line numbers here are changed as fourmolu shifted the lines

[Unisay]

This one too, we need to fix it.

[Unisay]

99% good, but some comments got detached from their bindings and floated to the top of a module in one file.

[SeungheonOh]

Turns out there is a bug in ourmolu/fourmolu that makes all comments get pushed to the very top if there's a OPTIONS_GHC pragma in the middle of the code. Found a workaround: one can wrap the pragma to disable fourmolu like following:

{- FOURMOLU_DISABLE -}
{-# OPTIONS_GHC -Wno-incomplete-patterns #-}
{- FOURMOLU_ENABLE -}

[Unisay]

Turns out there is a bug in ourmolu/fourmolu that makes all comments get pushed to the very top if there's a OPTIONS_GHC pragma in the middle of the code. Found a workaround: one can wrap the pragma to disable fourmolu like following:

{- FOURMOLU_DISABLE -}
{-# OPTIONS_GHC -Wno-incomplete-patterns #-}
{- FOURMOLU_ENABLE -}

Do you mind linking a bug in the fourmolu repository in the comment in our code so that we can remove the workaround once its fixed?