Bugfix for FlairTagger when using certain input formats.

[raykyn]

What's in the PR

• In the old version of the script, I fixed the problem with whitespaces in a pretty hackish way. This commit cleans this up, which solves a bug that occured for me when using certain input formats, where my hack failed to work properly.
• The old implementation also restricted the flair tagger to only tag tokens as defined by the whitespaces, this is now solved as well.

How to test manually

• e.g. Import a text as CAS XMI in Inception, observe that interpunctuation will not be part of the span tagged by the recommender.

Automatic testing

• [ ] PR includes unit tests
• see my last PR about not being able to get the testing environment running

Documentation

• [ ] PR updates documentation

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 0% with 28 lines in your changes are missing coverage. Please review.

Project coverage is 51.62%. Comparing base (9cca892) to head (6219a19).

Files	Patch %	Lines
ariadne/contrib/flair.py	0.00%	28 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #62 +/- ## ========================================== - Coverage 51.96% 51.62% -0.35% ========================================== Files 24 24 Lines 889 895 +6 ========================================== Hits 462 462 - Misses 427 433 +6 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[reckart]

see my last PR about not being able to get the testing environment running

Do you still have that problem?

[reckart]

@raykyn Please when you open a PR:

• create an issue

• make sure you have the latest version of our main branch

• create a new branch e.g. bugfix/XXX-name-of-issue from our main branch

• when you commit, please use the following format for you commit messages:

  
  #XXX - Name of issue

• change 1

• change 2

• ...

That would greatly facilitate the merge process for me.