Release preparations

[andreasabel]

• Remove vanilla Setup.hs files (legacy)
• Drop support for GHC 7 and LTS < 9.21
• Add READMEs to direct toward the tasty test framework

@sol I am accepting reformulations of the READMEs if you want to suggest some, see

• Deprecate in favor of tasty? #62

Closes #71, closes #72.

[andreasabel]

@sol Would you suggest a rewording of the READMEs?

As I understood from #62, tasty is kind of the "heir" of test-framework as it is compatible in the way functions are named.
However, alternatives are of course worth mentioning.

[andreasabel]

I had a phone conversation with @sol resulting in a new README.

[sol]

I think we should directly link to the README. I opened a PR against your branch for that:

#76

Other than that, this looks great. Thank you Andreas! 🙏🎉

[Bodigrim]

It would be helpful to guide users how to migrate to modern frameworks. Here is an instruction for tasty:

### Migration to `tasty`

The following steps are sufficient for the majority of packages:

* Replace packages in `build-depends`:
  * `test-framework` -> `tasty`,
  * `test-framework-hunit` -> `tasty-hunit`,
  * `test-framework-quickcheck2` -> `tasty-quickcheck`.
* Replace module imports:
  * `Test.Framework` -> `Test.Tasty`,
  * `Test.Framework.Providers.HUnit` -> `Test.Tasty.HUnit`,
  * `Test.Framework.Providers.QuickCheck2` -> `Test.Tasty.QuickCheck`.
* Replace in type signatures:
  * `Test` -> `TestTree`.
* Replace `defaultMain tests` with `defaultMain (testGroup "All" tests)`.

[sol]

This section is for "new users" and kept brief on purpose.

1. For existing users, there is no need to necessarily migrate to anything.
2. If existing users choose to migrate to something else, I trust them to be able to figure out themselves how to do this.
3. If you want to provide instructions on how to migrate from test-framework to your project then I think this belongs into the documentation of your project.

[sol]

Also, for what it's worth:

### Migration to `hspec`
The following steps are sufficient:
 * Add to `build-depends`:
   * `hspec-test-framework`
 * Remove from`build-depends`:
   * `test-framework`
   * `test-framework-hunit`
   * `test-framework-quickcheck2`
 * Replace `test-framework-th` with `hspec-test-framework-th`

But really, I don't think any of this belongs here.

[andreasabel]

I merged your suggestions.
Also -Wall is now sitting in cabal.project rather than the .cabal files, so we release with only the standard warnings on (minus -Wdeprecations).

[sol]

LGTM 👍

[andreasabel]

Candidates:

• https://hackage.haskell.org/package/test-framework-0.8.2.1/candidate
• https://hackage.haskell.org/package/test-framework-quickcheck2-0.3.0.6/candidate

[andreasabel]

Published!