[#285] Bump `text` package after 2.0.1 (to 2.0.2)

[Martoon-00]

Description

In the current master (after 2.0.1 version) text package changes implementation of pack, and this affects which rewrite rules should we use. After the new release, these and maybe some other changes will have to be applied.

Related issues(s)

Resolves #285

✓ Checklist for your Pull Request

Ideally a PR has all of the checkmarks set.

If something in this list is irrelevant to your PR, you should still set this checkmark indicating that you are sure it is dealt with (be that by irrelevance).

• [ ] I made sure my PR addresses a single concern, or multiple concerns which are inextricably linked. Otherwise I should open multiple PR's.
• [ ] If I added/removed/deprecated functions/re-exports, I checked whether these changes impact the .hlint.yaml rules and updated them if needed.

Related changes (conditional)

• Tests

  • [ ] If I added new functionality, I added tests covering it.
  • [ ] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.

• Documentation

  I checked whether I should update the docs and did so if necessary:

  • [ ] README
  • [ ] Haddock

• Record your changes

  • [ ] I added an entry to the changelog if my changes are visible to the users and
  • [ ] provided a migration guide for breaking changes if possible

Stylistic guide (mandatory)

• [ ] My commit history is clean (only contains changes relating to my issue/pull request and no reverted-my-earlier-commit changes) and commit messages start with identifiers of related issues in square brackets.

  Example: [#42] Short commit description

  If necessary both of these can be achieved even after the commits have been made/pushed using rebase and squash.

✓ Release Checklist

• [ ] I updated the version number in universum.cabal.
• [ ] I updated the changelog and moved everything under the "Unreleased" section to a new section for this release version.
• [ ] If any definitions (functions, type classes, instances, etc) were added, I added @since haddock annotations.
• [ ] (After merging) I created a new entry in the releases page, with a summary of all user-facing changes.
  • I made sure a tag was created using the format vX.Y.Z

[gromakovsky]

@Martoon-00 this PR won't be needed until text > 2.0.1 is released, did I get it right?

[Martoon-00]

Right.

This information seems not actual at the moment of me answering though, since even text-2.0.2 has been released.

[Martoon-00]

I'm not really sure whether commenting out the badges is what we want - when we make a release they won't be excluded from Hackage until the next release :thinking: